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

SV: Re: Feature request

From: Hans-Emil Skogh <Hans-Emil.Skogh_at_tritech.se>
Date: 2007-02-26 12:33:38 CET

> This is one reason why the suggestion of being able to
> record commit comments at the point of deciding to make
> the change, rather than retrospectively, could be
> advantageous.

This is usually where an issue tracking software comes in. You use the
issue tracker to track what changes you want to make and why. You use
the version tracking software to track exactly how this change was
implemented and when.

I do not think TSVN should attempt to be an issue tracker, there are
already others excelling in that area.

> I also like that idea because it seems more natural to me for
> a sequence of events to be 1) decide to make a change, 2) note
> that the change is going to be made, 3) implement the change,
> as opposed to 1) decide to make a change, 2) implement the change,
> 3) use diffs to work out what was changed.

A problem with your preferred method is that if you change your mind
while implementing, you will have to go back and edit your pre-composed
commit message. If you forget to do that, you will have a commit message
with false information.

> This can lead to vague and even inaccurate log messages, with
> commit messages applied to more files than were truly affected
> by a change or useless messages.

If you do the diffing properly there should be no such problem. And each
commit should apply to a single change. There is no need to specify
changes on a file-scope basis. The exact changes can always be found by
diffing. Try instead to write a commit message that in general terms
answers the question of "How did I implement feature X" where feature X
is described in your issue tracking software. (And you will of course
add a reference to the issue you are implementing.)

If you want to save time by taking notes as you go along just use your
favourite text editor, but you should still diff all your changes one
more time and verify your notes before committing.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Feb 26 12:34:08 2007

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

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