Re: C++-compat clean build

[Tom Tromey <tromey@redhat.com>]

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Jan> It is not a requirement but the preference is to post the patches
Jan> inlined in the mail text; just I am not sure Thunderbird will not
Jan> corrupt it, your mail body is format=flowed which would corrupt it,
Jan> OTOH without format=flowed some mailers wrap the patch to some
Jan> fixed column.  So maybe the attachment is the least worst for
Jan> Thunderbird.

These days what I do is write the email and ChangeLog entry into the git
commit message; then use git send-email to send the whole series.  This
requires minimal configuration and in particular doesn't need MUA
tweaking.

Then when the time comes to apply, I use git cvsexportcommit, and edit
in the ChangeLog entries by hand.  This step is a pain.

Finally, I've taken the lead from Pedro and Joel and use the .msg file
that cvsexportcommit leaves as the commit text.

I've tried a number of workflows over the years.  I find that this one
has the least amount of make-work; but naturally YMMV.

Tom