Mark Phippard wrote:
>>I'm having the darnedest time parsing this.
>>
>>Allow me to be more verbose about what I was thinking:
>>
>> - Make a branch in the main Subversion repository (at
>> svn.collab.net) based on the 1.1.x branch. Call the branch
>> /branches/ebcdic/.
>>
>>
>
>What I would like to see is a branch created named
>/branches/ebcdic/branches/1.1.x that is copied from the 1.1.x branch. We
>would only synch this with the main branch when new releases are made, such
>as 1.1.4.
>
>Then, at some point further down the road, I would copy trunk to
>/branches/ebcdic/trunk and start porting our code from the 1.1.x branch
>back to the trunk. We would first work on porting the code, and probably
>just commit it all in a handful of commits, depending on how well that
>goes. All of the locking code will be in there at the point we do this, so
>that will be a lot of new code to evaluate and port.
>
>
Since you won't develop any new features on those branches, I propose a
somewhat different naming scheme; either:
/branches/ebcdic-trunk
/branches/ebcdic-1.1.x
or
/ebcdic/trunk
/ebcdic/1.1.x
i.e., put the ebcdic port on the top level alongside /trunk, /tags and
/branches. If anyone thinks this is too radical, remember that the
repository structure is here to serve us, not the other way around.
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Feb 12 03:56:01 2005