[cvsnt] Re: Keyword Expansion Issues
Mike Amundsen
mike at amundsen.com
Wed Aug 21 04:01:27 BST 2002
Tony:
well, actually, i like the way SourceSafe reports for $Header: $. It
reports the complete repository info (the path in the repository), not just
the RCSfile.
I was just hoping to get the module information without also getting the
physical disk location.
oh well, thanks for the help.
MCA
"Tony Hoyle" <tmh at nothing-on.tv> wrote in message
news:3d5d18bc.92465734 at news.cvsnt.org...
> On Fri, 16 Aug 2002 11:07:33 -0400, "Mike Amundsen"
> <mike at amundsen.com> wrote:
>
> >I'm using the Keyword expansion features of CVSNT in my source code:
> >
> >// $Header: $
> >
> >expands to:
> >
> >// $Header: X:/CVSROOT/ProjectA/Components/Constructors.cs,v 1.1
2002/07/28
> >16:24:13 JoeDeveloper Exp $
> >
> >notice that the expansion includes the *physical* drive mapping and a
> >*actual* folder path. this seems incorrect to me. well, at least it's
not
> >what i had expected.
> >
> >is there a way i can 'tweak' the output to only name the repository and
> >module hierarchy instead of publishing the acutal location of the files
on
> >the server?
> >
> That's the way it's supposed to work:
>
> `$Header$'
> A standard header containing the full pathname of the RCS file,
> the revision number, the date (UTC), the author, the state, and
> the locker (if locked). Files will normally never be locked
> when
> you use CVS.
>
> You probably want to use:
>
> `$Id$'
> Same as `$Header$', except that the RCS filename is without a
> path.
>
> Tony
>
More information about the cvsnt
mailing list