Occasionally someone raises the non-sequential rev# thing, and its
usually for one of two reasons: build numbers and documentation
revision. Apparently some users get worried when a doc number of
build number goes from 1234 to 1567 in a single jump. Usually, this
can be fixed by pointing out that the only really important thing
(which svn provides as a strong guaranteee) is that newer versions of
a document have numerically greater revision numbers.
In fact, in this situation, I usually sell the "virtues" of the
single rev# model -- when you go to a release of a set of files/
documents, they are automatically get the same rev#, so you can
easily tell at a glance that two docs do or do not come from the same
release -- very nice.
--Tim
On Nov 14, 2006, at 3:24 AM, Eric wrote:
> At 02:38 AM 11/14/2006, Tim Hill wrote:
>
> <TH>>>>>Why are your users raising hell? What is the workflow that
> needs per-file rev# info?<<<<<
>
> Good morning, Tim.
>
> I'm not sure. I guess it's just that we're all accustomed to per-
> file rev numbers. And for documents, it does make some sense.
> That's why we're looking for something else to use for documents.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 14 18:40:36 2006