From: "Ævar Arnfjörð Bjarmason" <avarab@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 15:35:54 +0000 [thread overview]
Message-ID: <AANLkTin-x01FrFWLD04um8xwKeb6vUjpqlG0S7Xnk85j@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiksAOpFG3vGVGcbeZ0NcpQ5FbDjnZ7yDxUsAY_r@mail.gmail.com>
On Tue, Jul 27, 2010 at 15:31, Tong Sun <suntong@cpan.org> wrote:
> - work on the code, commit, hack, commit, hack, commit -- commit often
> & commit small
So far so good.
> - when AOK and need to integrate patches into main branch, squash all
> patches into one
That's just silly. Why is the policy to destroy commit information
when submitting patches?
next prev parent reply other threads:[~2010-07-27 15:36 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 [this message]
2010-07-27 15:43 ` Tong Sun
2010-07-27 15:39 ` Ramkumar Ramachandra
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=AANLkTin-x01FrFWLD04um8xwKeb6vUjpqlG0S7Xnk85j@mail.gmail.com \
--to=avarab@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).