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

Re: [TSVN] One Comment History Bug? Two Comment History Suggestions.

From: SteveKing <stefankueng_at_gmail.com>
Date: 2004-10-27 12:43:56 CEST

On Wed, 27 Oct 2004 12:38:04 +0200, Roland Erbs <r.erbs@niros.com> wrote:

> One bug?
> Comment History shows items from two Working Copies:
> On my client computer I have two different repositories checked out. I have
> committed and tagged files in both repositories. I select Merge/Branch on
> the Trunk directory of the WC of one of the repositories.
> In the Merge/Branch dialog, the Comment History has entries from both WCs
> not just the current one. I suppose this is a bug.

The comment history is global, not working copy or repository
specific. It shows all the log messages you've entered, no matter for
which working copy.

> Suggestion 1.
> It would be nice with a blank line in the Comment History so that when you
> select this blank line the Log Message edit box is not changed. As it is
> now, if you have written a message and just want to check the Comment
> History then the message you have written is gone since you cannot
> not-select an message from Comment History.

That's already changed. If you select an entry from the comment
history, it doesn't overwrite the current message anymore but is
inserted, i.e. the already entered message is appended to the selected
So if you select now an empty entry, nothing happens because something
'empty' is inserted.

> Suggestion 2.
> How about changing "Comment History" to "Log Message History"?



  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Oct 27 13:47:37 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.