From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: commit a1f6baa5 (wrap long header lines) breaks my habit
Date: Wed, 25 May 2011 17:40:46 +0200 [thread overview]
Message-ID: <20110525154046.GC7723@scotty.home> (raw)
In-Reply-To: <20110524200716.GF584@sigill.intra.peff.net>
Mail von Jeff King, Tue, 24 May 2011 at 16:07:16 -0400:
Hello,
> > > > git format-patch -k --stdout a..b | git am -k -3
> > >
> > > Why -k to am?
> >
> > Just first "-k", and "git am -3". Wrong in mind here at home before my
> > computer.
Wrong. I really typed the second "-k". (Local intelligence in
fingers.)
> Then it should preserve your long subject line just fine, as mailsplit
> (called by "am") will reassemble the folded line according to rfc822
> header folding rules.
>
> With "am -k", it does keep the fold. This is an artifact of the original
> behavior, where the folds were literally included from a multi-line
Correct, I checked this, so with
git format-patch -k --stdout a..b | git am -3
(no second -k)
all is as before.
Thanks for your clarification, sorry for the noise.
Stefan
Perhaps a little clarification like this:
commit e8069848dffe72579aa7f2c542e39fde9eab84b1
Author: Stefan-W. Hahn <stefan.hahn@s-hahn.de>
Date: Wed May 25 17:33:03 2011 +0200
format-patch: Clarify the behaviour of '-k'.
Added clarification in documentation of of 'git format-patch'.
When using 'git format-patch' together with 'git am' for rebasing,
'git am' should be called without '-k' if long subject lines should be
reassembled. This is neccesary, because a wrapping of long header lines
was introduced with commit:
commit a1f6baa5c97abc8b579fa7ac7c4dc21971bdc048
format-patch: wrap long header lines
Signed-off-by: Stefan-W. Hahn <stefan.hahn@s-hahn.de>
diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
index d13c9b2..4e62248 100644
--- a/Documentation/git-format-patch.txt
+++ b/Documentation/git-format-patch.txt
@@ -468,6 +468,16 @@ the current branch using 'git am' to cherry-pick them:
------------
$ git format-patch -k --stdout R1..R2 | git am -3 -k
------------
++
+In this example the subject lines of the commits will be folded after
+78 characters and 'git am' will keep this folding.
++
+To preserve long subject lines, 'git am' will reassemble the folded
+lines according to rfc822 if called without '-k' like this:
++
+------------
+$ git format-patch -k --stdout R1..R2 | git am -3
+------------
* Extract all commits which are in the current branch but not in the
origin branch:
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.
next prev parent reply other threads:[~2011-05-25 15:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:02 commit a1f6baa5 (wrap long header lines) breaks my habit Stefan-W. Hahn
2011-05-24 16:27 ` Junio C Hamano
2011-05-24 16:46 ` Stefan-W. Hahn
2011-05-24 20:07 ` Jeff King
2011-05-25 15:40 ` Stefan-W. Hahn [this message]
2011-05-26 20:36 ` Jeff King
2011-05-26 20:41 ` [PATCH 1/3] t: test subject handling in format-patch / am pipeline Jeff King
2011-05-26 20:53 ` [PATCH 2/3] mailinfo: always clean up rfc822 header folding Jeff King
2011-05-26 20:55 ` [PATCH 3/3] format-patch: preserve subject newlines with -k Jeff King
2011-05-26 21:18 ` Junio C Hamano
2011-05-26 21:19 ` Jeff King
2011-05-26 22:24 ` Jeff King
2011-05-26 22:27 ` [PATCH 3/5] pretty: add pp_commit_easy function for simple callers Jeff King
2011-05-26 22:47 ` Junio C Hamano
2011-05-26 22:27 ` [PATCH 4/5] clean up calling conventions for pretty.c functions Jeff King
2011-05-26 22:28 ` [PATCH 5/5] format-patch: preserve subject newlines with -k Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110525154046.GC7723@scotty.home \
--to=stefan.hahn@s-hahn.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).