On Tue, Oct 29, 2013 at 10:11 AM, Hari Shreedharan < [email protected]> wrote:
> You can submit patches with jiras being blocked by the other. When you > submit a patch, mention that the 2nd patch depends on the first one. > Unfortunately, review changes might cause the 2nd patch to be no longer > directly applicable and might require a rebase. > This won't be a case very often. Agree that Review changes would create confusion. Let me try something simple, create patch and send review request without dependency. Once review completes, I would rebase the patch, if needed. Will try to keep things simple for Committers. thanks ashish > > > Thanks, > Hari > > > On Monday, October 28, 2013 at 7:46 PM, Ashish wrote: > > > Folks, > > > > What would be best way to submit multiple patches? > > > > #1 Submit one and wait for it to be committed before submitting 2nd one > > #2 Submit patches as they are ready > > #3 Any other suggestion? > > > > The reason I ask is, I have 2 patches in review and almost ready with > next > > 2. Want to know what would work out well Flume Dev's, so that I can align > > my workflow accordingly. > > > > -- > > thanks > > ashish > > > > Blog: http://www.ashishpaliwal.com/blog > > My Photo Galleries: http://www.pbase.com/ashishpaliwal > > > > > > > -- thanks ashish Blog: http://www.ashishpaliwal.com/blog My Photo Galleries: http://www.pbase.com/ashishpaliwal
