Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of curt.arnld@gmail.com designates
 209.85.212.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=Aj+oF/jFkiKft2EGnbOh3LYVuN5W0KkziNMMzUC6GMkqHLYa19T36BZAHum1rLVyYv
         kBWjK9Z/yEj3bljeQBel0BsCH3J5RUEv4fVIka+Fp84Ck40d9XgnwDZnW9f0hMe6DptZ
         euyMELh8X14OPqPle1LMNq6r3SKyRd/TNFo3Y=
Sender: Curt Arnold <curt.arnld@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: svn commit: r948664 - in
 /logging/log4j/branches/BRANCH_2_0_EXPERIMENTAL/rgoers/log4j2-core/src/main/java/org/apache/logging/log4j/core:
 ./ appender/ filter/
From: Curt Arnold <carnold@apache.org>
In-Reply-To: <64BBA2A5-4284-43C1-9D73-48B39EA31373@dslextreme.com>
Date: Thu, 27 May 2010 08:49:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <29F5E105-8DC8-4FD9-A2E8-2363713E37BD@apache.org>
References: <20100527032632.0F7CB2388993@eris.apache.org>
 <09E1C1B2-6091-4E60-83A9-BC8359498D05@dslextreme.com>
 <1D4BF1AD-BE98-4AC6-9689-0CCBD4C37778@apache.org>
 <64BBA2A5-4284-43C1-9D73-48B39EA31373@dslextreme.com>
To: "Log4J Developers List" <log4j-dev@logging.apache.org>


On May 27, 2010, at 5:55 AM, Ralph Goers wrote:
>=20
> I know you mentioned getting git set up.

Raised it with infrastructure at =
https://issues.apache.org/jira/browse/INFRA-2743, part of the response =
was:

> To create and checkout a local "log4j2" branch that tracks the remote =
"BRANCH_2_0_EXPERIMENTAL" branch, use "git checkout -b log4j2 =
origin/BRANCH_2_0_EXPERIMENTAL".=20

It looks like it is missing something, but might point someone who is =
more git knowledgeable to a working approach.


> One thing that would help here is instead of simply adding comments =
(which I don't mind), for you to fork the code and make some of the =
changes you are suggesting or simply have ideas about. Trying out your =
own ideas might a) either clear up your questions, b) provide an =
alternative that is better or c) just give us two options instead of =
one.


I'm going to have to check how far I got in the code that I committed vs =
how far I had thought in my mind.  Most likely, I'd try to continue =
building on my earlier code and try to reach a point where appenders =
built on its interfaces could be wired into existing log4j as a test =
harness and maybe flesh out some of my thoughts on the API.

> =20
>=20
> Ideally, you and I shouldn't be the only two involved in this. Anyone =
else participating on this list should definitely join in.
>=20
> Ralph
>=20

Two is an improvement over one.   If we can get a things a little =
clearer, we could try to reach out of other ASF projects that use =
logging to document their pain points, wishes, requirements, random =
thoughts and maybe gain some additional voices if not contributors.=

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