Mailing-List: contact repository-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: repository@apache.org
Received-SPF: pass (nike.apache.org: domain of carlossg@gmail.com designates
 209.85.198.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=gB8s5lhyQb6Mp2M8zVee/6fyg1OHt0CX/1clCCq6n57Y5uLcoQcZKIQwQruQiibyFmUYlBUOJohWA//ENHRGIPgGJGjsImMxNtVU2586JdZOUnARjVklbO2VD1jZW77XKMEiv7kOxuk851pUol7o6+sj/kRwoqpBSZOYhUuXM/4=
Message-ID: <1a5b6c410711281831m6441303coa06c03863f3abd77@mail.gmail.com>
Date: Thu, 29 Nov 2007 10:31:51 +0800
From: "Carlos Sanchez" <carlos@apache.org>
Sender: carlossg@gmail.com
To: repository@apache.org
Subject: Re: apache-log4j-extras-1.0
In-Reply-To: <24F879C1-C04D-498A-B6E0-37B0CA53E414@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C6EFA593-0ED6-4299-B3AF-466E87572338@apache.org>
	 <1a5b6c410711272328h3b6b4b47pa15c3130c14264f2@mail.gmail.com>
	 <24F879C1-C04D-498A-B6E0-37B0CA53E414@apache.org>

done

On Nov 29, 2007 5:27 AM, Curt Arnold <carnold@apache.org> wrote:
>
> On Nov 28, 2007, at 1:28 AM, Carlos Sanchez wrote:
>
> > you can put it in the m2 repo, and you should if it's build with
> > maven, but you gotta let me know to setup the sync as only org/apache
> > is sync by default
> >
> > On Nov 28, 2007 5:05 AM, Curt Arnold <carnold@apache.org> wrote:
> >> I've just noticed that apache-log4j-extras 1.0 wasn't in the master
> >> repo.  I thought that I had placed it in the rsync repo when it was
> >> released back in early September, but can't confirm that and maybe I
> >> just forgot.  However, I wanted to ask here in case it was rolled
> >> back
> >> for some reason.
> >>
> >> If I just forgot, my plan is to copy the release from /www/
> >> people.apache.org/builds/logging/repo/log4j/apache-log4j-extras/1.0
> >> to /www/people.apache.org/repo/m2-ibiblio-rsync-repository/log4j/
> >> apache-log4j-extras/1.0.  log4j releases have been put in the m1
> >> repo,
> >> would there be a problem with having the log4j releases propagated
> >> from the  m1 and the apache-log4j-extras and other companion releases
> >> propagated from the m2?  Could the upcoming log4j 1.2.16 be placed in
> >> the m2 rsync repo?
> >>
> >>
>
> I've copied apache-log4j-extras from our staging repo to the m2-
> ibiblio-rsync-repository.  Please sync.  Thanks.
>


-- 
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                             -- The Princess Bride