[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 17:30:41 CEST

cmpilato@collab.net wrote:

>Sergey <sergeyli@pisem.net> writes:
>>This feature also enables the scenario where a coder would be able
>>to easily collect files from different directories that have changed
>>in regards to feature 1, and remove files that changed in regards to
>>feature 2, which must go in a separate commit. Without such feature
>>a coder would rely on memory to pick files from those that have
>>changed, which is statistically by far less reliable than that of a
>This argument makes no sense.
Thank you :-)

> In neither scenario is "a PC" making
>the decision about what to commit. It's that same coder, simply
>putting off a decision he was going to make at the command-line until
>his editor pops up, and then making that decision. And how is he
>going to decide what stays in the commit? Well, he'll examine the
>paths in the commit message -- you know, the exact same way he'd have
>made the decision at the command-line using the output from 'svn
The only difference being the list of files that have changed in front
of him/her, not in the head (waiting to be overlooked).

>The only real benefit is that we've saved the guy from having to type
>in a bunch of paths at the command-line. Now we can all argue the
>value of that benefit, but let's not make it sound like this feature
>is the saving grace from a world tainted by icky humans and their
>faulty circuits.
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.
Repeat for second commit. Another scenario is when both changes are
scattered among several directories: "hyper" is changed for "super" in
dir1/foo and dir2/bar, a new feature implemented in dir1/extrafoo and
dir2/minibar. Instead of typing, one would pick the suitable lines and
plunge ahead.
As I said, please do not overestimate coder discipline in other projects.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 17:32:09 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.