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

Re: PATCH: $Header$ handling + existing BUG of $HeadURL$ now also in $Header$?

From: C.A.T.Magic <c.a.t.magic_at_gmx.at>
Date: 2004-07-22 19:09:16 CEST

Alexander L. Belikoff wrote:
> $Header$ has very clear advantages over $Id$.

in SVN, the $Id$ keyword has lost a bit of information
in comparison to CVS: the _branch_ of the file.

$Id: file.txt 2 2004-07-22 16:22:50Z cat $

$Id: file,v 2003/12/04 20:38:11 cat Exp $

in svn's $Id$ its hard (or impossible?) to tell if
the file came from trunk or from a branch.
in cvs it is clearly visibly because you see
the 4-digit version number "".

but there is also a negative side to using $Header$ in SVN:
because $Header$ alsways contains the full repository path,
it is also containing the 'TAG' path.
$Header: /Tags/foo-20040501/test.txt,v 5 2004/07/22 16:39:38 cat Exp $
$Header: /Tags/foo-20040608/test.txt,v 8 2004/07/22 16:39:38 cat Exp $

this means that you get different file content for _all_ files,
dependent on the tag you used to checkout the file,
even if the rest of the file is identical.
In CVS the path and version always remains the same if the file is

does this patch ensure that svn switch visits ALL files containing
$Header$ and update them correctly?
$HeadURL$ is already buggy in this regard:

( the following assumes Repos/file.txt and
   a tag created from it as Repos/TAG/file.txt
   exists )

#>cat file.txt
   $HeadURL: file:///Repos/file.txt $

#>svn switch file:///Repos/TAG/file.txt file.txt

#>cat file.txt
   $HeadURL: file:///Repos/file.txt $

^^^^ but this should now be Repos/TAG/ !

#>del file.txt
#>svn update file.txt
#>type file.txt
   $HeadURL: file:///Repos/TAG/file.txt $

^^^^ only works if file is deleted first.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 22 19:09:31 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.