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

RE: [TSVN] latest revisions in revision graph

From: Jens Peters <jpeters7677_at_gmx.de>
Date: 2005-11-04 20:56:53 CET

> Define "latest revision" please. Every branch which isn't
> removed has a "latest" revision as HEAD, because it still
> exists in HEAD.

May be "last commited revision" in a branch/tag/trunk is a beter name. I
could imagine something like this:

25(HEAD)
|
| 17
| 15 |
| | |
| |branch1.1 (Rev12)
| |
| |
|branch1 (Rev 10)
|
|tag1 (Rev5)
|
trunk

                27(HEAD)
                | 26
25 | |
| |tag2(Rev24)
| 15 |
| | |
| |branch1.1 (Rev12)
| |
| |
|branch1 (Rev10)
|
|tag1 (Rev5)
|
trunk

I hope the schemas explaine what I mean. In the second one you can see a
commit on a tag (should never happen, but it is of course possible).

Show Log on a branch (thus rev 10 or 12 on the second schema) should fetch
the log from the revision where the copy has happened only (since this is
only one log entry it could be shown in the rectangle representing the
branch, eg the first 100 chars and the rest as tool tip), while show log on
the latest commited revision (thus Rev 25, 15,27,26) should fetch all log
messages from this branch or trunk.

I'm interested in your/other thoughts.

> That's a good idea:
> http://tortoisesvn.berlios.de/issues/?do=details&id=184
>

Thanks a lot!

Greetings,
Jens

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Nov 4 20:57:15 2005

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.