You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Oleg Kalnichevski <ol...@apache.org> on 2008/03/17 19:24:23 UTC
Commit policy
Folks
I am currently in the process of making some fairly non-intrusive
changes to the NHttp transport reducing the amount of code duplicated
between HttpComponents and Synpase and improving debug logging in the
transport components.
Do you want me to submit a patch, commit those changes to branch or
commit them directly to the trunk? What is the usual commit policy for
Synapse?
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Commit policy
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Oleg
> I do not expect any merging conflicts as my changes affect logging
> decorators and IO event dispatchers only. That should not interfere with
> your work.
>
> I'll commit my changes tonight or tomorrow the latest
>
Cool.. go ahead whenever you get the time
thanks
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Commit policy
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Tue, 2008-03-18 at 05:56 +0530, Asankha C. Perera wrote:
> Oleg
>
> I have some local changes on nhttp on my machine at the moment. If you
> have already done any changes, you can commit them directly , and I
> can merge my changes, if you haven't yet started with the changes, let
> me know and I will commit what I have..
>
Asankha,
I do not expect any merging conflicts as my changes affect logging
decorators and IO event dispatchers only. That should not interfere with
your work.
I'll commit my changes tonight or tomorrow the latest
Oleg
> thanks
> asankha
>
> Paul Fremantle wrote:
> > Oleg
> >
> > Commit directly to the trunk is fine. If you think the changes are
> > large, please discuss the strategy and approach. We operate "commit
> > and review" at the moment, tho of course with the new TLP status those
> > policies are up for review.
> >
> > Paul
> >
> > On Mon, Mar 17, 2008 at 6:24 PM, Oleg Kalnichevski <olegk@apache.org> wrote:
> >
> > > Folks
> > >
> > > I am currently in the process of making some fairly non-intrusive
> > > changes to the NHttp transport reducing the amount of code duplicated
> > > between HttpComponents and Synpase and improving debug logging in the
> > > transport components.
> > >
> > > Do you want me to submit a patch, commit those changes to branch or
> > > commit them directly to the trunk? What is the usual commit policy for
> > > Synapse?
> > >
> > > Oleg
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > > For additional commands, e-mail: dev-help@synapse.apache.org
> > >
> > >
> > >
> >
> >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Commit policy
Posted by "Asankha C. Perera" <as...@wso2.com>.
Oleg
I have some local changes on nhttp on my machine at the moment. If you
have already done any changes, you can commit them directly , and I can
merge my changes, if you haven't yet started with the changes, let me
know and I will commit what I have..
thanks
asankha
Paul Fremantle wrote:
> Oleg
>
> Commit directly to the trunk is fine. If you think the changes are
> large, please discuss the strategy and approach. We operate "commit
> and review" at the moment, tho of course with the new TLP status those
> policies are up for review.
>
> Paul
>
> On Mon, Mar 17, 2008 at 6:24 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
>
>> Folks
>>
>> I am currently in the process of making some fairly non-intrusive
>> changes to the NHttp transport reducing the amount of code duplicated
>> between HttpComponents and Synpase and improving debug logging in the
>> transport components.
>>
>> Do you want me to submit a patch, commit those changes to branch or
>> commit them directly to the trunk? What is the usual commit policy for
>> Synapse?
>>
>> Oleg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>>
>
>
>
>
Re: Commit policy
Posted by Paul Fremantle <pz...@gmail.com>.
Oleg
Commit directly to the trunk is fine. If you think the changes are
large, please discuss the strategy and approach. We operate "commit
and review" at the moment, tho of course with the new TLP status those
policies are up for review.
Paul
On Mon, Mar 17, 2008 at 6:24 PM, Oleg Kalnichevski <ol...@apache.org> wrote:
> Folks
>
> I am currently in the process of making some fairly non-intrusive
> changes to the NHttp transport reducing the amount of code duplicated
> between HttpComponents and Synpase and improving debug logging in the
> transport components.
>
> Do you want me to submit a patch, commit those changes to branch or
> commit them directly to the trunk? What is the usual commit policy for
> Synapse?
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org