As part of the preparations for this move I have tagged the HEAD of logging-log4j as so:

cvs rtag TAG_CHAINSAW2_MOVE logging-log4j

cheers,

Paul

Paul Smith wrote:

Thanks Ceki for doing this.

I was in the last phase of preparing the module when Ceki reminded me that we can copy the CVS history over if we do some funky CVS tricks. My local repository had just copied the files. We would have had the history in the logging-log4j module, but not in logging-chainsaw module, and I agree with Ceki that the history is worth keeping together.

So, it's just going to take a touch longer than I thought to get this together. Scott, if you have any changes, could you bundle them as patches and fire them over to me?

I have also modified the log4j build process to clean out any Chainsaw related stuff to keep log4j nice and clean, I'll submit that at the same time when I feel it's ready to roll.

One silly thing I just realised was that I had not tested the log4j unit tests BEFORE making the change, just to make sure they all succeed. I assume that they still do... ? I just want to make sure that if they don't work it's because of my changes, and not because of an existing problem. If someone could confirm everything's a-ok, that would be great.

I'll try and get this sorted out today, but not sure how that will go with what else I have on at work.

cheers,

Paul

Ceki G�lc� wrote:

At 06:36 AM 2/24/2005, Paul Smith wrote:

ok, only Ceki's vote to go, and I understand he's still recovering from some hardware problems. In a recent mail, Ceki intimated he was, in principle, in favour, so I will _begin_ this process locally, but not commit, and wait until Ceki has a chance to cast his vote.



The CVS module 'logging-chainsaw' has been created, appropriate karma granted.


I'll send a message to [email protected] to inform the rest of Logging Services.



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to