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

Re: Feature request

From: Nick Lindridge <nick_at_ioncube.com>
Date: 2007-02-22 16:05:39 CET

km0form02@sneakemail.com writes:

> So what I'm proposing is this:
> An entry in the shell extension, which says 'checkin notepad' (or
> something similar). This entry brings up an editor with a text field,
> similar to the one shown in the commit dialog. All you really do there is
> to edit the next checkin message. This message is stored globally for the
> project's root directory, and is visible again in the commit dialog
> (either as default, or as one of the suggestions).
> So what do you think? Neat feature or dumb idea?

Something along these lines is a very good idea and would be an exciting
feature, as even if making daily or intra-daily commits, it can be
impossible to remember why changes were made and running diffs on every
file is often required. Code comments should be added as you go, and
commit messages could similarly be written just after or even before a
change is made. As it stands, it takes a long time to commit when you have
to run diffs on every file and reconstruct why changes were made, and this
becomes tedious very quickly as well as error prone.

As you described, an option to accumulate text into what will become the
checkin message would be required, as well as a way to review and edit the
message both on a single and multiple file basis, i.e. see all files with
pending checking messages as well as changed files with no pending
message. Finally a feature to do a mass commit where the prewritten
messages get applied to their associated files unless there is no message.
In the latter case, there could be a choice of behaviour such as commit
with no message, skip the commit for unmessaged files with warnings, or
prompt for a message in a way similar to current behaviour.

This could dramatically speedup the checkin procedure at the end of the
day of whenever the commits happen, and is also likely to give more
accurate commit messages.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Feb 22 16:06:12 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.