Subject: Re: $NetBSD$ Version Control Keyword
To: Curt Sampson <firstname.lastname@example.org>
From: Michael Graff <email@example.com>
Date: 07/22/1996 14:38:47
Curt Sampson <firstname.lastname@example.org> writes:
> Could someone please explain to this novice at version control why
> we use the keword $NetBSD$ instead of $Id$ in the NetBSD source
> files, how this is done with CVS, and what the ramifications are
> for users who want to use version control on NetBSD at home?
I would suspect it is for two reasons.
1) it lists the true origin, so when other people pick it up they can
refer back to the original NetBSD source, and
2) it lists NetBSD. :)
> I've got a personal patch or two patches to the NetBSD kernel and
> userland, and I'm getting a bit sick of sup wiping them out every
> night. I'd like to be able to hang on to them somehow. I'm thinking
> that putting the NetBSD revisions in the vendor branch of a CVS
> repository and then ocasionally doing an import from my sup copy
> might help here (though it still seems to mean that I've got to
> keep an entire separate copy of the source--*sigh*). Am I even
> heading in the right direction here?
What do the patches do? Are they of common interest?
BTW, I did just that for some time... a local CVS repository I supped
sources into nightly. It worked. :)