From: Tong Sun <suntong@cpan.org>
Date: Tue, 27 Jul 2010 15:43:02 GMT
Subject: Re: Recommended work flow with git to send in patches
Message-ID: <AANLkTikk_EZuGayD2yPqEhTyXS9YKHscwCF2NNjXwMdv@mail.gmail.com>
In-Reply-To: <AANLkTin-x01FrFWLD04um8xwKeb6vUjpqlG0S7Xnk85j@mail.gmail.com>

On Tue, Jul 27, 2010 at 11:35 AM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> 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?

Sorry about the confusing. The original message was composed under the
condition that all patches are relevant patches that work together to
form a big logical changes. I was required to do the squashing.

thanks