This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: C++-compat clean build
- From: Tom Tromey <tromey at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Ondrej Oprala <ooprala at redhat dot com>, "'gdb-patches\ at sourceware dot org'" <gdb-patches at sourceware dot org>
- Date: Thu, 03 Oct 2013 14:39:00 -0600
- Subject: Re: C++-compat clean build
- Authentication-results: sourceware.org; auth=none
- References: <524AB12E dot 8090209 at redhat dot com> <20131001125338 dot GA12847 at host2 dot jankratochvil dot net>
>>>>> "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