From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Tong Sun <suntong@cpan.org>
Cc: git@vger.kernel.org
Subject: Re: Recommended work flow with git to send in patches
Date: Tue, 27 Jul 2010 21:09:03 +0530 [thread overview]
Message-ID: <20100727153901.GA5351@kytes> (raw)
In-Reply-To: <AANLkTiksAOpFG3vGVGcbeZ0NcpQ5FbDjnZ7yDxUsAY_r@mail.gmail.com>
Hi Tong,
Tong Sun writes:
> 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.
-- Ram
next prev parent reply other threads:[~2010-07-27 15:40 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 [this message]
2010-07-27 15:47 ` Tong Sun
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=20100727153901.GA5351@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=suntong@cpan.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).