Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of mfncooper@gmail.com
 designates 64.233.184.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=cqjcpd+wtPLLmBarSKrTuFXwYsg1ZvH0JMprWbdQgbIxK2QZ95a50WTOL11iA4LjDXNdGHeaxj7Cfmjipa2dFid0Mgf3L+pKYOZBobxem4vUictao5QE0BbKY4QNHxrbUaJfQBSXtHz9R4GGOApqBSZdlbqqRfftOEfZplv9CjU=
Message-ID: <16d6c62004121817465e491c33@mail.gmail.com>
Date: Sat, 18 Dec 2004 17:46:02 -0800
From: Martin Cooper <mfncooper@gmail.com>
Reply-To: Martin Cooper <mfncooper@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: Jakarta Commons Structure rehashed
In-Reply-To: <31cc373604121817344e60cf3a@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <8E2D018A78A5A04095667ADF098FF29A03DEA15A@ms06>
	 <41C49174.10105@lfjr.net> <16d6c62004121814134d82b805@mail.gmail.com>
	 <31cc373604121817344e60cf3a@mail.gmail.com>

On Sat, 18 Dec 2004 20:34:47 -0500, Henri Yandell <flamefew@gmail.com> wrote:
> Use case for wanting to get all tags and branches for one component is
> promotion from sandbox->proper, proper->jakarta, jakarta->TLP. Or the
> opposite, which I hesitate to call demotion :)

Yah, good point. Then I guess I like Option A as long as someone can
come up with a viable way of checking out all the trunks at once.

--
Martin Cooper


> Hen
> 
> 
> On Sat, 18 Dec 2004 14:13:49 -0800, Martin Cooper <mfncooper@gmail.com> wrote:
> > On Sat, 18 Dec 2004 21:22:12 +0100, Emmanuel Bourg <smanux@lfjr.net> wrote:
> > > Tim O'Brien wrote:
> > > > Not following this one, this implies that ASF has one trunk.  Even
> > > > though copies are cheap I wouldn't want to create a copy of the entire
> > > > SVN tree for every release.
> > >
> > > Err I thought Jakarta would have its own SVN repository, thus the trunk
> > > would be "Jakata-wide" and not "ASF-wide".
> >
> > No, as Noel indicated, the repo is ASF-wide.
> >
> > > Also I don't think we have to
> > > copy the entire tree when tagging/branching, the copy just the component
> > > tree :
> > >
> > > tags/
> > >     digester-1.8/
> > >         commons/
> > >             digester/
> > >     configuration-1.1/
> > >         commons/
> > >             configuration/
> >
> > If this works, this might be a very good option. (I have no reason to
> > think it wouldn't work, but I don't know SVN well enough to be sure
> > one way or the other.) It would make it simple to check out everything
> > in Commons, and easy to tag and branch. The only disadvantage I can
> > think of is that it wouldn't be easy to get all tags and branches for
> > just one component, but I'm not sure I see a use case for that anyway.
> >
> > --
> > Martin Cooper
> >
> >
> > > Emmanuel Bourg
> > >
> > >
> > >
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org