[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: RFC: Revision indexes for 1.1

From: Garrick Olson <Garrick.Olson_at_Aceva.com>
Date: 2004-04-24 02:56:36 CEST

--- Branko Cibej [mailto:brane@xbc.nu] wrote:
>4.1 Extend the format of the "-r" command-line option
>Currently the -r command-line option accepts a revision number or a
> -r revnum|{date}[:revnum|{date}]
>The {date} specifier is internally converted to a revision number. We
>another specifier, [labelname], that is also converted to a revision
>Note: Since label values are non-unique, a [label] specifier can refer
to a
>list of revision numbers. Such lists useless for "svn update" or "svn
>however, "svn merge" could be extended to handle multi-revision merges
>(cherry-picking, right?). We should support an analogous format,
>"-r revnum,revnum,..." for specifying an explicit list of revision
>this is also needed for defining multi-revision labels.

Actually, if you make the semantics of commands like "svn update"
like "-r max(revnum,revnum,...)" you get another feature for free:
levels. This is very handy for people with automated build servers,
can then label a successfully built revision as, say, "stable". A
can then easily update to the latest good code rather than HEAD, which
could be broken:

$ svn up -r stable

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 24 02:56:52 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.