You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Rob Hawkes <ro...@gmail.com> on 2007/07/01 21:54:34 UTC
Revision numbers as MAJOR.MINOR.PATCH?
Heya,
How can I make subversion output revision numbers in a
MAJOR.MINOR.PATCH method rather than 1, 2, 3, 4, 5, 6.. etc?
Regards,
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Revision numbers as MAJOR.MINOR.PATCH?
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Sunday 01 July 2007 23:54, Rob Hawkes wrote:
> How can I make subversion output revision numbers in a
> MAJOR.MINOR.PATCH method rather than 1, 2, 3, 4, 5, 6.. etc?
...another 2cc:
When you tag your project, the revision number becomes part of the URL,
e.g. /tags/myproject/myproject-2.11.42. Using consistent naming for tags and
branches will allow you to extract the revision number.
Other than that, as already pointed out, the repository revision number is not
useful for things like this.
Uli
--
Sator Laser GmbH
Geschäftsführer: Ronald Boers, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Revision numbers as MAJOR.MINOR.PATCH?
Posted by Rob Hawkes <ro...@gmail.com>.
Thank you for pointing that out, It looks like I'll stick with the SVN
way of doing things then.
On 02/07/07, Andy Levy <an...@gmail.com> wrote:
> Please remember to use Reply To All so discussion stays on-list.
>
> On 7/1/07, Rob Hawkes <ro...@gmail.com> wrote:
> > Thank you for replying.
> >
> > The reasoned I asked is I wanted to know how people like phpBB and
> > Drupal managed to get the revision number to display differently.
> >
> > Here are their $Id$ outputs respectively.
> >
> > $Id: index.php,v 1.172 2007/06/11 00:11:02 acydburn Exp $
> >
> > $Id: install.php,v 1.34 2007/01/10 10:15:07 unconed Exp $
> >
> > As you can see, they use the major.minor version numbering.
>
> These projects appear to use CVS, not Subversion.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Revision numbers as MAJOR.MINOR.PATCH?
Posted by Andy Levy <an...@gmail.com>.
Please remember to use Reply To All so discussion stays on-list.
On 7/1/07, Rob Hawkes <ro...@gmail.com> wrote:
> Thank you for replying.
>
> The reasoned I asked is I wanted to know how people like phpBB and
> Drupal managed to get the revision number to display differently.
>
> Here are their $Id$ outputs respectively.
>
> $Id: index.php,v 1.172 2007/06/11 00:11:02 acydburn Exp $
>
> $Id: install.php,v 1.34 2007/01/10 10:15:07 unconed Exp $
>
> As you can see, they use the major.minor version numbering.
These projects appear to use CVS, not Subversion.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Revision numbers as MAJOR.MINOR.PATCH?
Posted by Andy Levy <an...@gmail.com>.
On 7/1/07, Rob Hawkes <ro...@gmail.com> wrote:
> Heya,
>
> How can I make subversion output revision numbers in a
> MAJOR.MINOR.PATCH method rather than 1, 2, 3, 4, 5, 6.. etc?
Subversion revision numbers count the number of commits made to the
repository. You can't "make" it do anything else, unless you want to
hack on the source for a while and create your own version that does
it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Revision numbers as MAJOR.MINOR.PATCH?
Posted by Talden <ta...@gmail.com>.
I go out of my way to avoid the development content being bound to any
release number. Only at actual release time is a given stabilised milestone
assigned the product version that the general populace need to know about.
That way, milestones can be regular occurrences and QA and product
management, independent of development can decide if the feature-set of a
given milestone warrants an actual public release.
Of course, this model suits us, it won't necessarily suit everyone.
Don't expose the users to details of your SCM. If you changes SCMs or even
the processes by which you use it, users should not notice (well apart from
quality and/or productivity improvements since that's the only reason you
change right).
--
Talden
On 7/2/07, Rob Hawkes <ro...@gmail.com> wrote:
>
> Heya,
>
> How can I make subversion output revision numbers in a
> MAJOR.MINOR.PATCH method rather than 1, 2, 3, 4, 5, 6.. etc?
>
> Regards,
> Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>