IGI/Michael Möllney wrote:
> Hi Stefan
> Stefan Küng wrote:
>> IGI/Michael Möllney wrote:
>>>> 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.
>> Sorry, but that's not possible and would even be wrong in the revision
> Is is technically not possible?
Technically it's of course possible. But it would require a *lot* of
searching and therefore would make the graph *extremely* slow. In fact
so slow that most users couldn't use it anymore.
> Due to our conversation about the RevisionGraph I understand that
> revisions are repository wide, thanks for that enlightenment.
> I already understood this when I wrote my last mail. Please accept that
> I understand this now and see my questions not in the
> impression, that I do not understand this fact.
> So in this understanding let me ask a question. It is not a rhetorical
> or offensive question:
> There seems to be a difference in effect.
> What is the difference in the repository at rev12 if I copy a tag from
> trunk@10 or trunk@11?
> In what aspect does the tag@12 look different?
In your case, it's not different. But there are cases where it can be
different. And there's no way to find out if it *really is not
different* as it is in your case.
> Despite from the fact that revisions have to be seen repository wide:
> The commit log feature of subversion distinguishes the path: you only
> see the logs that are relevant to a path.
> You do not see every revision log of the repository. And this is good,
> else it would be too confusing.
>>> And that is the point. Why would I like to see the log of branch@11
>>> if this has no relation to trunk@11 ?
>> If you open the log dialog, you will see immediately the last
>> committed revision.
> And this is exactly the point. This is the information I want to see in
> relation to trunk, but I see a log from a different branch if I hover
> over the shown trunk@11.
Yes, the log message of that revision.
But the log message you're interested in is shown if you hover over the
target of the copy operation (i.e. the tag you created).
>>> 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
>> It wouldn't be consistent but wrong. The graph doesn't show the last
>> committed revisions but the copy relations of urls. Using the last
>> committed revisions would mean to show wrong information.
> Maybe you are right and it is a bad habit of me that I just use HEAD in
> a copy of trunk to tag, even though the HEAD revision number was not
> created by a commit to the trunk path.
> But every tool in TortoiseSVN seems to respect this.
Not really. *Most* do, but not all.
And if you show the log for the tag, you will see in the revision where
the tag was created in the bottom pane of the log dialog a line like
/tags/mycreatedtag (copied from /trunk: rev 11)
So that information is used in the graph.
> Let me turn it the other side round:
> How can I bring the graph to a state, that I would like to see?
> Do I have to set the copy to a specific revision number (e.g. the rev.
> number that was created with the last commit to the trunk path)?
> So wouldn't it be nice to have a shortcut in the copy panel for:
> "Take the revision number of the last commit for the 'from:" path"
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jul 27 20:37:58 2006