Re: Recommended work flow with git to send in patches

From: Tong Sun <suntong@cpan.org>
Date: Jul 27, 2010, 15:47 UTC
Message-ID: <AANLkTinEQKuxHD6MbXq43E=AWymebvoWXM5v2Tm6vejw@mail.gmail.com>
In-Reply-To: <20100727153901.GA5351@kytes>

On Tue, Jul 27, 2010 at 11:39 AM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

Show 9 quoted lines

>> Compressing my "life long story" into a single question -- what's the
>> recommended work flow to work with git and send in patches, when
>> upstream might be slow in respond, and require squashing relevant
>> patches into one?
>
> Personally, I use `git symbolic-ref` to create a new branch without
> history, stage and create commits to send off to the list from there;
> it's also worth noting that I keep the branch to fixup my commits and
> re-roll after reviews.

Thanks a lot for the comment.

Could you elaborate it a bit with actual commands, starting from 'git pull git://remote/project master' please?

I'm new to git and the above comment barely helps me to put all jigsaw puzzle together.

thanks