[2122] in Kerberos_V5_Development
Re: Thoughts about CVS tagging conventions
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Wed Dec 18 19:07:03 1996
Date: Wed, 18 Dec 1996 19:06:53 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: Marc Horowitz <marc@cygnus.com>
Cc: "Theodore Y. Ts'o" <tytso@MIT.EDU>, krbdev@MIT.EDU
In-Reply-To: Marc Horowitz's message of 18 Dec 1996 18:56:41 -0500,
<t53g213e79i.fsf@rover.cygnus.com>
From: Marc Horowitz <marc@cygnus.com>
Date: 18 Dec 1996 18:56:41 -0500
[ I'm forwarding Marc's response to krbdev at his request.]
"Theodore Y. Ts'o" <tytso@MIT.EDU> writes:
>> It's not clear whether this should be started in the CVS repository or
>> not, since it contains meta-data about the CVS tags themselves. I don't
>> think this should be a problem, though. I propose we create a file in
>> the top-level of the CVS tree, called "cvs-tags".
You could have a file at the top level which lists PR's which are
fixed or addressed in some way, and store this file in CVS like any
other. Thus, at any given tag, the file will contain the right
information. This works with branches, etc., too.
True; this might also be useful, although this doesn't solve the
complete problem I was trying to deal with. For example: what the heck
is the tag "ORACLE_SNAPSHOT" for? (answer: it's a pre-beta 5 snapshot
that I gave to Oracle when they wanted to start working on their
product. This is the version of Kerberos which Oracle started from when
they created Oracle Secure Network Services, which secures their
networked SQL product.)
It would be useful to have a file which expanded tags into their full
meanings....
- Ted
