>>>>> "Greg" == Greg A Woods <[EMAIL PROTECTED]> writes:
>> easily. And this is virtually free. Tags also makes fills the
>> output of "cvs log -h" with rubbish.
Greg> Something like that is only rubbish if it doesn't mean
Greg> anything to you.
Greg> To me those dates you would use are just rubbish since I
Greg> can't know for sure that they represent a well known
Greg> boundary or milestone in development.
I also use tags for marking milestones.
However, I was previously talking about tags that are automatically
generated at *regular* time intervals (e.g. at 04:00 of every working
day). I once tried that practice, but eventually found that not
useful, as I would run out of good and meaningful tag names unless I
use systematic ones such as May18, May19, May20. But then, why not
check out by date&time?
For milestones, it's not that difficult to make a good and
self-describing tag name. Moreover, milestones are usually erect at
irregular and often unpredictable times. This is where "co -D"
doesn't fit, and tags are appropriate. I think tags are invented for
this, rather than "periodically making a snapshot". The latter can be
done with "co -D", without the hassles of inventing and managing tag
names.
Greg> To me the tags I would use represent very well known points
Greg> in the temporal state of the repository -- points that don't
Greg> rely on having to remember (or write down in some other
Greg> place) a timestamp.
Yes, this is what tags are for.
--
Lee Sau Dan §õ¦u´°(Big5) ~{@nJX6X~}(HZ)
.----------------------------------------------------------------------------.
| e-mail: [EMAIL PROTECTED] http://www.csis.hku.hk/~sdlee |
`----------------------------------------------------------------------------'
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
