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

Re: [PATCH][RESEND] Issue #1295 (take 5)

From: Sergey A. Lipnevich <sergeyli_at_pisem.net>
Date: 2003-05-14 18:29:54 CEST

cmpilato@collab.net wrote:

>"Sergey A. Lipnevich" <sergeyli@pisem.net> writes:
>>Consider a documentation directory with 150 xml files all named
>>similarly: chaper{001-150}.xml. If you've made changes in twenty five
>>of them to replace "hyper" with "super", and in another three to
>>describe a new feature, you'll have to first lookup what has changed
>>(step 1), and then commit separately (steps 2-3). Having such a
>>feature removes step 1: bring up the commit editor, sort out
>>unnecessary files, commit.
>See, this is the part of your argument that doesn't make sense. How
>does this coder "sort out the unnecessary files"? By "looking up what
>has changed" in those files. Don't you see, he *is* doing step 1 in
>both scenarios, just at different times. The only way he can truly
>skip step 1 is if he already knows which paths were part of which
>group of changes, in which case this reverts to what I stated as the
>only benefit of this system (see below, or my previous message).
The difference I'm talking about is the one (e.g. in a restaurant)
between knowing what's on the menu and having the menu in front of you.
If you're a fequent guest or you always know what you want, you won't
need a menu. If you want to refresh your memory or want to look up
what's there to make sure you didn't miss anything. I'm assuming you
know what's inside each dish (file) once you see the name.

>Right. Which is *exactly* the one benefit I mentioned:
> "The only real benefit is that we've saved the guy from having to
> type in a bunch of paths at the command-line."
No, the benefit of collecting all changes for coder's observation before
committing *and* allowing this coder to alter it.

>And likewise, please do not understate the steps in your scenarios so
>that they suit your particular argument.
Obviously you guys have more experience in dealing with version control
systems as well as with adding new features to Subversion. I know just
one thing for sure: I'm a die hard CVS fan (even though I don't know all
its features) who has to use Perforce because of how SourceMage project
is hosted, and editing a file list before committing is one of the
fetaures I actually appreciate. I think it's logical because it allows
productive use of something that is static in CVS: list of files that
have changed.

Thank you!

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 18:31:06 2003

This is an archived mail posted to the Subversion Dev mailing list.

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