Formatt

["EXT-Raiteri, Ashley L" <as...@boeing.com>]

i Strongly concurr with that (single pass), but that means that martin has
to do it all at once very quickly, otherwise merge problems will occurr.
Perhaps a Weekend would be a good time to do it, closing the code on friday
morning, with a warning to everyone that might be working on patches, and
then submitting the changes across the board for a rev drop on a monday
morning.
ash

-----Original Message-----
From: Daniel Rall [mailto:dlr@finemaltcoding.com]
Sent: Friday, March 08, 2002 9:11 AM
To: rpc-dev@xml.apache.org
Subject: Re: [request] new commiter


Martin Poeschl <mp...@marmot.at> writes:

> why don't you want the code to be (re)formatted??
> do you like the code as it is??

Not particularly, but won't I don't like are tons of random code
reformatting changes in the CVS diffs, especially when they're mixed
with code changes (Jon! ;-).  But if everyone else is in favor of it
I'd withdraw my objects if you can hold the changes to a single pass
over the code.

> which coding conventions should be used for xmlrpc??

I like Turbine's.  ;)


- Dan

Re: Formatt

[Martin Poeschl <mp...@marmot.at>]

EXT-Raiteri, Ashley L wrote:
> i Strongly concurr with that (single pass), but that means that martin has
> to do it all at once very quickly, otherwise merge problems will occurr.
> Perhaps a Weekend would be a good time to do it, closing the code on friday
> morning, with a warning to everyone that might be working on patches, and
> then submitting the changes across the board for a rev drop on a monday
> morning.
> ash

sounds like a plan ;-)

martin


> 
> -----Original Message-----
> From: Daniel Rall [mailto:dlr@finemaltcoding.com]
> Sent: Friday, March 08, 2002 9:11 AM
> To: rpc-dev@xml.apache.org
> Subject: Re: [request] new commiter
> 
> 
> Martin Poeschl <mp...@marmot.at> writes:
> 
> 
>>why don't you want the code to be (re)formatted??
>>do you like the code as it is??
> 
> 
> Not particularly, but won't I don't like are tons of random code
> reformatting changes in the CVS diffs, especially when they're mixed
> with code changes (Jon! ;-).  But if everyone else is in favor of it
> I'd withdraw my objects if you can hold the changes to a single pass
> over the code.
> 
> 
>>which coding conventions should be used for xmlrpc??
> 
> 
> I like Turbine's.  ;)
> 
> 
> - Dan

Re: Formatt

[Martin Poeschl <mp...@marmot.at>]

EXT-Raiteri, Ashley L wrote:
> i Strongly concurr with that (single pass), but that means that martin has
> to do it all at once very quickly, otherwise merge problems will occurr.
> Perhaps a Weekend would be a good time to do it, closing the code on friday
> morning, with a warning to everyone that might be working on patches, and
> then submitting the changes across the board for a rev drop on a monday
> morning.
> ash

sounds like a plan ;-)

martin


> 
> -----Original Message-----
> From: Daniel Rall [mailto:dlr@finemaltcoding.com]
> Sent: Friday, March 08, 2002 9:11 AM
> To: rpc-dev@xml.apache.org
> Subject: Re: [request] new commiter
> 
> 
> Martin Poeschl <mp...@marmot.at> writes:
> 
> 
>>why don't you want the code to be (re)formatted??
>>do you like the code as it is??
> 
> 
> Not particularly, but won't I don't like are tons of random code
> reformatting changes in the CVS diffs, especially when they're mixed
> with code changes (Jon! ;-).  But if everyone else is in favor of it
> I'd withdraw my objects if you can hold the changes to a single pass
> over the code.
> 
> 
>>which coding conventions should be used for xmlrpc??
> 
> 
> I like Turbine's.  ;)
> 
> 
> - Dan