Re: Commit ID Enhancement

[Todd Denniston]

Derek Robert Price wrote:
> 
> 
> It occurred to me that a "Commit ID" implemented as a tag might make a
> useful addition to the CVS feature-set.
>From my perspective, only a minor improvement, as it only builds into cvs
something that I can do as frequently or seldom as I (as the cm person on
several projects) chose.

> 
> If a unique commit id tag were applied to each revision as it is
> committed (unique across the repository and the same for each file in
> a commit), this might be a useful step towards the merge/change set
> tracking some people have proposed.
> 
> Such a special tag could be accessed to back out a single commit,
> implying something like `up -j <cid> -j <<cid> -1>' when used alone to
> back out a single, complete, "change".
> 
> I would think that either a new namespace and new options // to or
> syntax involving -r & -j would be in order or a namespace outside the
> current tag namespace, perhaps using names that start with a character
> currently prohibited in tags.  I definately prefer the latter but I
> have not examined all the implications of that change.
> 
How about instead of reserving a namespace _from_ all users of CVS, allow them
to specify in a file (in $CVSROOT/CVSROOT/????) the pattern that they want
used.
their header and global number:
"boneheadedCommitNumber%n"

or if they want it based on each user (this might be a really stupid thing)
but global number:
"%uTrashedUsAt%n"

or if they don't want it happening automatically at all:
""

if they just want what ever you come up with:
"DEFAULT_PATTERN"

and of course I would prefer that the file default to "" most times.

also with the current implementation of tags the tag would need applied across
the whole repository, because if they wanted to checkout against the tag they
only get those tags that were tagged with that tag... not a problem with diffs
though.  BTW I am not suggesting changing the current implementation of
checkout against tags, I use that effect when I want only a particular set of
files checked out for tests but want all available for development.

> Just an idea in case anybody has any spare time on their hands.
Not enough spare time to do anything other than grump. :}

> 
> Cheers,
> 
> Derek
> 
Oh, and no spaces allowed in the pattern 8P

-- 
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane) 
Harnessing the Power of Technology for the Warfighter