Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Gerhard Fiedler wrote: > Peter Crowther wrote: > > > CVSNT's revision numbers [...] may be invisible in the next > release, > > so don't rely on them. > > Really? I frequently use them for verification that I and > someone else are talking about the same revision of a file. > Maybe remove the useless "1.", but please leave something > like a unique revision number. I second that. Users need some way to identify a specific revision within the repository. Commit IDs won't do it, because we also need to identify whether commit ID 3684523170647ec is more recent or less recent than commit ID 9084522e5a0269c. Timestamps could be used, but they are much more cumbersome than a simple two or three digit number. When trying to track down a particular change that's no longer current (i.e. 'cvs annotate' won't work) I frequently use 'cvs di -rX -rY', with X and Y starting at reasonable guesses, and narrowing down via a binary search to the specific revision I need. -- Jim