You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Greywolf <gr...@starwolf.com> on 2009/09/29 09:46:55 UTC
internal dynamic link ("alias")
Greetings, all,
I've looked and I don't see a way to make this happen, so I thought
I'd post and a) see if anyone else thinks this makes sense and b)
if it does make sense, if it is possible to integrate.
I have my three branches (well, two, technically) set up:
Dev/Main
Dev/$DEV_VERSION (typically major.minor.dev-rev)
Release/$RELEASE_VERSION ($DEV_VERSION with only the first two components)
I would like to have a way internally to track a given branch as "LATEST"
or whatever other label I should like to give it; i.e. have it so that
instead of referencing a specific revision, it will actually link to the
head of a working branch which I could then assign the symbolic name
"LATEST".
I can do this in the filesystem for my own internal use, but it would be
nice to do it in-tree so that I can point other people to this dynamic
target, i.e. "Hey, just go to https://.../svn/Dev/LATEST" and it will
automatically pick up the changes.
I know I can work within LATEST instead, but then I don't have a referent
branch giving me the versioning I want to maintain -- I really do have
a need for this.
Thank you in advance for the courtesy of a reply.
--*greywolf;
--
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401547
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: internal dynamic link ("alias")
Posted by Stein Somers <ss...@opnet.com>.
Greywolf wrote:
> I have my three branches (well, two, technically) set up:
>
> Dev/Main
> Dev/$DEV_VERSION (typically major.minor.dev-rev)
> Release/$RELEASE_VERSION ($DEV_VERSION with only the first two components)
>
> I would like to have a way internally to track a given branch as "LATEST"
I imagine that when you create say Release/7.0, it is actually a copy of a
carefully scrutinized development revision? Then when you create that copy
Release/7.0, create a second copy Release/LATEST after deleting the old
Release/LATEST. You can do this all at once with the svnmucc command.
--
Stein
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401562
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].