summaryrefslogtreecommitdiff
path: root/builtin
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2011-05-26 20:41:18 (GMT)
committerJunio C Hamano <gitster@pobox.com>2011-05-26 21:11:59 (GMT)
commit00ebc977484e18c03160b6319322858c088bce55 (patch)
tree5a1a1aeb93bd358ac0b0e7f4a332e809076bdaf1 /builtin
parent990f6e30eb00adeb8cad75c3be34c0fc9ff6abb0 (diff)
downloadgit-00ebc977484e18c03160b6319322858c088bce55.zip
git-00ebc977484e18c03160b6319322858c088bce55.tar.gz
git-00ebc977484e18c03160b6319322858c088bce55.tar.bz2
t: test subject handling in format-patch / am pipeline
Commit a1f6baa (format-patch: wrap long header lines, 2011-02-23) changed format-patch's behavior with respect to long header lines, but made no accompanying changes to the receiving side. It was thought that "git am" would handle these folded subjects fine, but there is a regression when using "am -k". Let's add a test documenting this. While we're at it, let's give more complete test coverage to document what should be happening in each case. We test three types of subjects: a short one, one long enough to require wrapping, and a multiline subject. For each, we test these three combinations: format-patch | am format-patch -k | am format-patch -k | am -k We don't bother testing "format-patch | am -k", which is nonsense (you will be adding in [PATCH] cruft to each subject). This reveals the regression above (long subjects have linebreaks introduced via "format-patch -k | am -k"), as well as an existing non-optimal behavior (multiline subjects are not preserved using "-k"). Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin')
0 files changed, 0 insertions, 0 deletions