Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of jorton@redhat.com designates
 209.132.183.28 as permitted sender)
Date: Wed, 6 Oct 2010 17:20:49 +0100
From: Joe Orton <jorton@redhat.com>
To: dev@apr.apache.org
Subject: Re: apr-util 1.5.x -> trunk
Message-ID: <20101006162049.GA28270@redhat.com>
Mail-Followup-To: dev@apr.apache.org
References: <20101005074049.GA10384@redhat.com>
 <4CAB6BAF.6080309@rowe-clan.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4CAB6BAF.6080309@rowe-clan.net>
User-Agent: Mutt/1.5.20 (2009-08-17)
Organization: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor,
 Berkshire, SL4 1TE, United Kingdom.
  Registered in UK and Wales under Company Registration No. 03798903
  Directors: Michael Cunningham (USA), Brendan Lane (Ireland),
 Matt Parson (USA), Charlie Peters (USA)

On Tue, Oct 05, 2010 at 01:17:19PM -0500, William Rowe wrote:
> On 10/5/2010 2:40 AM, Joe Orton wrote:
> > Any objection to renaming the apr-util 1.5.x branch to "trunk"?  It is 
> > the trunk for that tree now.
> 
> Let us know if Nick's suggested change satisfies, I've drafted a trunk
> which explains things...

I don't really need the status quo "explained" to me in a README file.  
I proposed to fix it, because it is (to me, obviously) broken.

1) The tip of development for the apr-util tree is what is currently 
branches/1.5.x.  Yes, most of that code also exists in the apr tree.  
apr-util releases and branches do not come from the apr tree, they come 
from the apr-util tree.

2) I have hard-coded into my brain the convention that the trunk is the 
trunk, not a branch named by its current version.  I also have scripts 
which make this assumption.

3) The trunk called branches/1.5.x will have to be renamed to a trunk 
called branches/1.6.x if 1.5.x gets cut.  Which is dumb.

4) Yes, "people" might get confused if they try to use apr-util's trunk 
with the APR 2.x, but, meh.  We are the people who use the VCS and it 
should be arranged for our convenience.

Regards, Joe