Re: storing cover letter of a patch series?

From: Jacob Keller <jacob.keller@gmail.com>
Date: Aug 15, 2016, 23:01 UTC
Message-ID: <CA+P7+xpVOMH6qa6j+oCizcWvO30t1zYA1MD3jkw-7yzw6SPy2w@mail.gmail.com>
In-Reply-To: <xmqqwpjhg42v.fsf@gitster.mtv.corp.google.com>

On Mon, Aug 15, 2016 at 1:38 PM, Junio C Hamano <gitster@pobox.com> wrote:

Show 10 quoted lines

> Jacob Keller <jacob.keller@gmail.com> writes:
>
>> Some people have suggested this simple idea, and I like it, but they
>> did mention that modifying the cover letter now requires a rebase over
>> a potentially large series of patches, which can get annoying.
>
> That can be simply solved by keeping the cover at the end.  When you
> are updating the real patch on the series with "rebase -i", you
> would have a chance to update the cover at the same time that way.
>

It has problems keeping it at the end as well because that makes regular commits and commit --amend funky.., but you could do squashes into the cover letter easily enough as suggested by Philip Oakley. I think that might be the most natural flow we have now that doesn't depend on creating some fancy new object type.

Thanks, Jake