On Tue, Jan 23, 2007 at 09:35:38AM +0000, Neil Williams wrote: > As commented elsewhere, normal release numbers do not have any date > component and you've still got the problem that multiple svn commits > are frequently made on the same day. The date, in this context, is just > misleading and would need to be a full UTC timestamp to have any real > meaning. The revision number is far more precise and just like a normal
My feeling is you're kinda nitpicking here, but let me play your game :) Unless you, as a Debian packager, are packaging a CVS/SVN/... snapshot whose date is "today" this is a bogus problem. Indeed if the date timestamp is at least yesterday [1] the amount of commit occurred until that day can no longer change. Using both CVS and SVN you can checkout/update your working copy up to that date without any possible confusion. Cheers. [1] i.e. yesterday or earlier in the time line -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ (15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the (15:57:15) Bac: no, la demo scema \/ right keys at the right time
signature.asc
Description: Digital signature
