git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tong Sun <suntong@cpan.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Recommended work flow with git to send in patches
Date: Tue, 27 Jul 2010 11:47:34 -0400	[thread overview]
Message-ID: <AANLkTinEQKuxHD6MbXq43E=AWymebvoWXM5v2Tm6vejw@mail.gmail.com> (raw)
In-Reply-To: <20100727153901.GA5351@kytes>

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

>> 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

  reply	other threads:[~2010-07-27 15:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 15:31 Recommended work flow with git to send in patches Tong Sun
2010-07-27 15:35 ` Ævar Arnfjörð Bjarmason
2010-07-27 15:43   ` Tong Sun
2010-07-27 15:39 ` Ramkumar Ramachandra
2010-07-27 15:47   ` Tong Sun [this message]
2010-07-27 16:45     ` Ramkumar Ramachandra
2010-07-27 17:11       ` Jakub Narebski
2010-07-27 17:28         ` Ramkumar Ramachandra
2010-07-27 17:35 ` Jakub Narebski
2010-07-27 19:48   ` Tong Sun
2010-07-28 16:49     ` Jakub Narebski
2010-07-28 22:40   ` Tong Sun
2010-07-28 23:20     ` Jakub Narebski
2010-07-28 23:30       ` Tong Sun

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTinEQKuxHD6MbXq43E=AWymebvoWXM5v2Tm6vejw@mail.gmail.com' \
    --to=suntong@cpan.org \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).