[cvsnt] Re: commit followed by a tag

[Tony Hoyle]

Matt Schuckmann wrote:
> If a developer knows that a set of files he's commiting is all related to
> one feature or fix or just wants to keep track of a set of changes he/she is
> making to the trunk (or a branch) (i.e. create a Change Set) why should it
> be a 2 step process to commit then tag. Every SCM system I've ever worked
> with before has had the capability to apply a tag (or label) at the time of
> 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.

Tony