Date: Mon, 30 Oct 1995 20:04:39 +1100 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, peter@jhome.dialix.com Cc: CVS-commiters@freefall.freebsd.org, cvs-gnu@freefall.freebsd.org, nate@rocky.sri.MT.net Subject: Re: cvs commit: src/gnu/usr.bin/rcs/rlog rlog.1 rlog.c Message-ID: <199510300904.UAA15212@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>> Yes it is :-). $Id$ is treated differently by `cvs export', so in the >> release, all files with $Id$ have gratuitous differences from the checked >> out versions. >Perhaps somebody could explain the logic behind this to me, as I >certainly do not understand why we do this.. I thought it was to preserve our Ids from other users' revision control systems. It's annoying when foreign revision control polices such as $Log$ in rcs get imported. Even for things like $Id$ that we want, we really want our Ids separate from the originals. >So, where does this 'cvs export' code come from? It looks very much like Don't know. >If we are worried about somebody cvs importing the source into their own >tree and loosing our $Id$ lines, IMHO that's not the way to do it - >$FreeBSD$ would be much better and just ship either the source tree that >was used in the 'make release' or use proper 'cvs co'.. Perhaps that should be $FreeBSD-Id$. What does $FreeBSD$ do exactly. I'd like one that is applied automatically to all files that we've changed from the vendor branch. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510300904.UAA15212>