Thanks Paul,
it's confirming what I read in the documentation. If you allow one extra
question: Can you tell how "expensive" it is to switch over my working
copy to the copy (i.e. branch/tag) in question, to then look into a
file's history to finally see how it looked like when the branch was
created?
Cause that is what I finally want to know (with least effort in time and
steps necessary): what state did a file have when a particular branch
was created. :o) I'm currently working with test data, so the repository
is not as heavily loaded as it will be when we're going productive.
Hendrik
> -----Original Message-----
> From: Paul Koning [mailto:pkoning@equallogic.com]
> Sent: Friday, January 13, 2006 4:14 PM
> To: Scheider, Hendrik
> Cc: users@subversion.tigris.org
> Subject: Re: Tagging and the trunk history
>
> >>>>> "Hendrik" == Hendrik Scheider <Scheider> writes:
>
> Hendrik> Dear all, when I branch/tag, however you name it, this
> Hendrik> action is only visible in the copy's history. How can make
> Hendrik> it appear in the trunks history as well?
>
> You can't. It's a copy operation, and copy is a change on the
> destination, not on the source. The trunk is the source, so the copy
> is invisible.
>
> This is a fundamental difference in approach vs. CVS. In CVS, tags
> and branches are attributes of a file, and the whole history tree of a
> file is in one place, with all the entries mixed together strangely.
> In Subversion, a tag or branch is a copy in the namespace. From any
> point in the namespace, you only see the history of the branch you're
> on (including the point prior to the copy point, i.e., the "fork in
> the history", unless you say --stop-on-copy). But you do NOT see the
> whole history tree, not unless you ask at the root of the repository.
>
> paul
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jan 13 18:19:15 2006