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

Re: [DESIGN] Aliases? (Was: RE: Re: I, too, miss tags.)

From: <robert_at_infotility.com>
Date: 2006-02-24 18:11:01 CET

Quoting "Gale, David" <David.Gale@Hypertherm.com>:

> Perhaps we could satisfy all of our former CVS-acolytes (myself
> included) with a "svn alias" command (or some such), which would assign
> a human-readable name to a specific revision. HEAD, PREV, and the like
> already exist, but there's currently no way to assign one of the user's
> own creation. I'd propose something like:
> svn alias [-force] [-r 21134] NEW_LABEL [path-to-repos]
> If the command is run within a working copy, the path to the repository
> should be picked up from that. If no revision is specified, HEAD should
> be assumed. If the NEW_LABEL alias already exists, an error should be
> thrown unless -force is specified (matches CVS's behavior). This
> doesn't change the working copy; it creates a versionless alias on the
> repository, which would then be available for future "-r <alias>"
> commands. I'd also suggest a "svn alias -list" command, which would
> list all of the aliases in the repository and the revisions they point
> to.

I think all of this is right on the mark.

Since we know already that symbolic aliases are useful
(HEAD, BASE, etc) why not set up a mechanism to allow
users to make new ones?

Various correspondents have suggested workarounds or
hacks of various kinds. Thanks guys, but if there's
evidence that there is widespread desire for this feature
(namely that it has been solved multiple times by
multiple persons) why not just build it into the standard release?

Thanks a lot to everyone who has responded.
I appreciate your help.

Robert Dodier

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 24 18:13:26 2006

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

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