Hmm... Well, I think I see your point, but it seems to me that it would be
easier to "browse" a tree of tagged versions where the tag name matches the
release version identifier? In other words, a customer tells me he has
version V003R089 firmware running in his piece of equipment and has bug XYZ.
In order for me to debug the problem, I have to go get a copy of that code,
yet I don't have a revision-number-to-release-version cross-reference unless
I tag all released versions, right? I certainly don't want to use the
subversion revision number as my release version identifier, right?
Otherwise I'll have customers asking me (for example) why the revision
number has jumpped by a hundred or a thousand (due to changes to other
products in the repository) and I never called them to tell them that there
was a new version of firmware available during all that time... I probably
should have said this up front, but we do somewhat custom source coding for
embedded processors, so just about every customer that comes along gets a
new version in the baseline (trunk) or "branch" of an existing version. I
guess "svn log" gives me that cross-reference list, but then I have to
cut-paste or re-type to actually get a particular revision, right?
Am I all wet, or is this making sense?
From: Ben Collins-Sussman [mailto:firstname.lastname@example.org]
Sent: Tuesday, March 23, 2004 1:34 PM
To: Crucius, Wesley
Cc: 'email@example.com'; 'Philip Martin'
Subject: Re: Thanks and a global versioning question; WAS:: Help: XML Parser
e rror, Date Conversion failed
On Tue, 2004-03-23 at 13:26, Crucius, Wesley wrote:
> On a side note, what do you think of the idea of a post commit script
> that automatically tags every commit? My proposed users aren't going
> to like (or
> understand) the global revision number so I'm hoping if I use a post
> script to create a "YYYYMMDDHHMMSS" sort of a tag, they may never notice
> global revision number...
Trying to make your users use Subversion without noticing/using the global
revision numbers is like asking them to drive a car after removing the
Besides, every global revision already *has* a date attached to it... so I
don't understand how it would be useful to present your users with a
directory full of subdirectories named "YYYMMDDHHMMSS"? That would be
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Mar 23 20:55:06 2004