james82@gmail.com wrote on 03/06/2006 01:59:33 PM:
> On 3/6/06, Mark Phippard <markp@softlanding.com> wrote:
> > We would like to make a branch where we can manage this version of the
> > port for Subversion 1.3.x as we will still have a need to produce
builds
> > for those users. Does anyone have any objections to this? Should I
just
> > make it under the existing ebcdic branch, or in a new namespace? I
have
> > no preference. I will also need to make tags eventually. I guess I
would
> > propose creating:
> >
> > /branches/ebcdic/v5r4/1.3.x
>
> Let me see if I understand.
>
> This new branch will contain the EBCDIC changes which you propose for
> 1.3.x. You're creating this branch because you want to quickly cut a
> 1.3.1 release for EBCDIC without burdening the Subversion team with
> the task of reviewing all of your EBCDIC patches in time for 1.3.1.
> If, in future, your EBCDIC patches are integrated into 1.3.x, we can
> retire this branch.
I realize this can be confusing.
We have had a number of patches accepted to trunk for building Subversion
on OS/400 V5R4. Obviously none of these are going to be backported to the
1.3.x branch. However, we still need to produce working builds of
Subversion 1.3.x for users of OS/400 V5R4. We cannot use the existing
EBCDIC branch for this, because that version only works on the older
versions of OS/400.
So I need a "permanent" branch just for Subversion 1.3.x on OS/400 V5R4.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 6 20:30:47 2006