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

[TSVN] Re: A simple request

From: Markus Wichitill <mawic_at_gmx.de>
Date: 2004-09-02 04:19:40 CEST

Stefan Küng wrote:
> Thomas Kindler wrote:
>> TortoiseSVN still seems to be lacking some things, that have been
>> implemented in TortoiseCVS for a long time (like the dropdown-history
>> of commit log entries for another example, etc..).
> That was requested once before. But I couldn't and can't see what that
> would be good for. And people requesting this couldn't explain it to me
> why they really want this. Why do you need "old" commit log messages?

I use the message history all the time in TCVS.

In an ideal world, one new feature/change in my software would only require
a single atomic SVN commit, but in the real world, I often have to make more
commits later that add missing pieces of the new/changed feature, but don't
require new messages, since they're part of the same issue. Or sometimes I
use a modified version of the original message, like "Added feature X
(forgot foo)".

In a similar "real development isn't as atomic as SVN would like to have it"
way, I often work on multiple features at once. Sometimes it's possible to
use separate working copies for those, but often that's not feasible. So for
example I have file #1 which has changes for feature A, file #2 which has
changes for features A and B, and file #3 which has changes for feature B
only. Since I don't want file #1 to have log messages about feature B, I
commit those three files separately, which means I have to use the same
message parts twice.

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Sep 2 11:21:25 2004

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.