diff options
| author | Patrick Ohly <patrick.ohly@intel.com> | 2016-11-29 09:55:10 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-07 10:36:10 +0000 |
| commit | 303a1aa3df43eb0b693d8602062fa33c4a08fdd6 (patch) | |
| tree | 96f7bbc8a4ab503abf8d99038143e50b4305e7f3 /meta/lib | |
| parent | 11063a01d4511b2688ea7ba2d7359e4e07328c66 (diff) | |
| download | openembedded-core-303a1aa3df43eb0b693d8602062fa33c4a08fdd6.tar.gz openembedded-core-303a1aa3df43eb0b693d8602062fa33c4a08fdd6.tar.bz2 openembedded-core-303a1aa3df43eb0b693d8602062fa33c4a08fdd6.zip | |
scripts/send-pull-request: Avoid multiple chain headers
When creating a patch set with cover letter using the
send-pull-request script, both the "In-Reply-To" and "References"
headers are appended twice in patch 2 and subsequent.
That's because git-format-patch already inserted them and then
git-send-email repeats that. Suppressing mail threading in
git-send-email with --no-thread avoids the problem and is the
right solution because it works regardless whether git-send-email is
called once or twicee.
Repeating these headers is a violation of RFC 2822 and can confuse
mail programs. For example, Patchwork does not detect a patch series
problem when there are these extra headers.
[YOCTO #10718]
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/lib')
0 files changed, 0 insertions, 0 deletions