Re: Repository Graph shows non existing trunk revision number

Hi Stephan

Stefan Küng wrote:

> IGI/Michael Möllney wrote:
> [snip]
>
>> Just in front: sorry for the lengthly answer...
>>
>> I think it is just about consistency in the TortoiseSVN then:
>>
>> When I look in the Reprobrowser:
>> tag says in Revision column: 12
>> branch says in Revision column: 11
>> trunk says in Revision column: 10
>> this looks to me as if this is the "head" of each branch individually.
>> Ok, there is only one rev 11 in the whole repository and in every
>> branch.
>> And I understand that revisions are repository wide.
>
>
> That column shows the 'last committed revision', i.e. the revision
> where that path was last changed in a commit. But that doesn't mean
> the path doesn't exist in other revisions too, even in HEAD (you
> browse usually the HEAD revision with the repobrowser, so all path you
> see there actually exist in the HEAD revision).

This is the information I would like to see in the RevisionGraph, too.
Set up the ReproBrowser to look at the repository at rev 12. You will
see number rev10 at trunk (not rev11).
So I would like to see the last committed revision on the "from:",
because that has the log attached to it that is reasonable.... the same
as I see in the log and in the ReproBrowser.
If I right click on the trunk rev11 and ask for the log the listing will
not show the rev11 in the log listing, but rev10.

So my idea:
File wise trunk@11 is equal to trunk@10. My copy was from trunk@head (=
rev11) but the last commit was rev10 at trunk path.
So my copy is file wise: tag@12 == trunk@12 == trunk@10 but it is !=
branch@11 !!!
And that is the point. Why would I like to see the log of branch@11 if
this has no relation to trunk@11 ?
The graph should just show me the revision numbers _exactly_ as the
ReproBowser at the revision number of the copy.
I am at rev12 at the copy and the last commit in trunk was trunk@10 but
not trunk@11.

Again I think it is about consistency with the other fine tools in
TortoiseSVN.

Kind regards,
Michael

>
>> If I look with svn log at the trunk at rev 11 then the log is empty.
>> If I look at the repository graph and stop the mouse over the
>> trunk->rev11 I can see the log of the rev 11 that has relation to the
>> branch only,
>> it tells me what the committing to the branch was about. And that
>> info is optically attached to the trunk.....
>> If I use TortoiseSVN to log the trunk I can not see any rev 11. I see
>> rev10 as the top most (one could think: head?).
>
>
> The log dialog only shows revisions where the selected path actually
> got changed. So you won't see a log entry for HEAD if the selected
> path wasn't just changed and committed.
>
>> My Impression:
>> I would not like to see a log of rev11 on the trunk if the log of
>> the trunk doesn't show rev11.
>> And I would not like to see a rev11 in the trunk in the revision graph.
>> Probably I should have chosen to copy rev.10 instead of HEAD and
>> everything would have been good.
>> But I would expect to see the revision and the log of the last commit
>> of the trunk, here rev10.
>
>
> But you explicitly told Subversion to create the tag from HEAD (you
> selected that entry in the branch/tag dialog), and the HEAD revision
> was 11 at that time. So Subversion did exactly what it was told. And
> the graph also shows exactly what you have done.
>
> Stefan
>

-- 
-----------------------------------------------
Dipl.-Math. Michael MÖLLNEY
Senior Software Developer
Ingenieur-Gesellschaft fuer Interfaces mbH
Langenauer Str. 46
57223 Kreuztal
Germany
Phone:    +49-2732-5525-0
Fax:      +49-2732-5525-25
E-mail:   m.moellney@igi-systems.com
Internet: www.igi-systems.com
          www.litemapper.com
-----------------------------------------------
The information sent by means of this e-mail
message is intended for the use of the
addressee only! Publication, duplication,
distribution and/or forwarding to third parties
of this message, as well as use of the
information by other persons than the intended
recipient, is strictly prohibited. If you have
received this communication in error, please
notify the sender immediately by returning it.
-----------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org