[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature Request: Option to *always* commit all the changes in the *entire* working copy.

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 3 Aug 2009 06:29:32 -0400

On Sun, Aug 2, 2009 at 17:19, Nick Sabalausky<business4_at_semitwist.com> wrote:
>>> I don't always realize until
>>> it's too late (ie the changes have already been replaced by newer
>>> changes,
>>> and that particular snapshot that I *thought* I committed is lost
>>> forever,
>>> and that particular revision is effectively corrupted.)
>>This makes no sense to me. What's "corrupted" and how? It's only your
>>working copy and nothing will be replaced that you don't ask for.
> The newly committed revision is corrupted. Ie, If I make a modification that
> involves changes to four files, I commit only two of those changed files,
> and someone checks out the revision I just made, then clearly it's unlikely
> to work.
>>> I consider this a very serious data loss problem. I need an option to
>>> disable that behavior and force all commits to auto-select all the
>>> changes
>>> in the working copy to be commited, and never just a subset of the
>>> changes.
>>How is your data lost?
> How isn't it? I'll explain again: I have file 'foo'. At this point we'll
> call it version A. I then make a change and now have B. I do a commit, and
> some other stuff gets committes, but 'foo' doesn't and since I expect
> commits to just work, I don't notice. So I continue and make another change
> and now have C. I then commit 'foo' C (successfully this time), and shut
> down for the day. At this point, 'foo' B is clearly gone.

"Corrupted" and "data is lost" implies that you took all the correct
actions, but the software scrambled/lost bits. What you're describing
is a function of user action which can easily be avoided by correct
user behavior. As I said previously, you're given plenty of
opportunities to review what you're committing before you do it.

Let's suppose for a moment that this option does exist, and in the
course of your "juggling a million things" you commit your whole WC,
committing changes that you didn't want because they were in the WC
and you didn't notice, just like you've been "corrupting" your data
today because you're committing too deep in the WC and not getting
changes higher up in the tree? What will you do then?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-08-03 12:29:44 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.