[cvsnt] Re: commit followed by a tag
matthew_schuckmann at amat.com
Fri Feb 4 18:46:17 GMT 2005
Ok, whats a bug and commit identifer, how do you create them, how do you see
them search for them.
How do you use them to check out etc.
I've seen nothing in any documentation on these.
"Tony Hoyle" <tmh at nodomain.org> wrote in message
news:cu0evf$jtq$1 at paris.nodomain.org...
> Matt Schuckmann wrote:
> > If a developer knows that a set of files he's commiting is all related
> > one feature or fix or just wants to keep track of a set of changes
> > making to the trunk (or a branch) (i.e. create a Change Set) why should
> > be a 2 step process to commit then tag. Every SCM system I've ever
> > with before has had the capability to apply a tag (or label) at the time
> > commiting the file to the repository, it just makes sense.
> That's different from tags. That's covered by bug and commit identifiers.
> Tags are for marking point releases not for tracking individual commits.
> Of course pullng out individual bugs as changesets has to be done with
> care - if you pull them out of order & they relate to common files you
> can get hard to fix conflicts.
More information about the cvsnt