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

Re: using $Header $ and $Log $

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-07-20 16:08:29 CEST

Stuart Arnold wrote:

> My script actually uses that field(filepath) to open the repository for the
> file
> It then retrieves the revision info(history/log) between an old build of a
> program and the newest one.
> It then generates reports from these results so we can confirm what went
> into a build.

Since you didn't state what portion of $Header$ you were using, I
couldn't speculate about what to suggest as an alternative. You will
need to rewrite any reports to hit the appropriate URL's for the
Subversion repository.

However, since Subversion is not file-based like CVS, your reports can
probably be more easily generated by using:

        svn log \
        http://server/path/to/old/release \

(beware linewraps). In other words, if you are following the suggested
repository layout for Subversion, instead of trying to use your CVS
model, you can get a log between two tags directly, rather than querying
each file individually.

> I guess what I'm getting to is that $Header$ keeps some "path" to its
> location in the repository and
> that it be consistent,eg, $HeadURL$ should be used for the "file" portion.

$HeadURL$ is the only way to the the path information for a given file.
  It is more consistent than the equivalent RCS information presented
from CVS since it is the actual URL needed to retrieve the log
information, as opposed to the relative pathname within the RCS/CVS



John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 20 16:08:50 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.