From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: git@vger.kernel.org
Subject: commit a1f6baa5 (wrap long header lines) breaks my habit
Date: Tue, 24 May 2011 18:02:53 +0200 [thread overview]
Message-ID: <20110524160253.GA7723@scotty.home> (raw)
Hello,
for rebasing I'm using normally
git format-patch -k --stdout a..b | git am -k -3
With commit
commit a1f6baa5c97abc8b579fa7ac7c4dc21971bdc048
format-patch: wrap long header lines
(since >v1.7.4)
this isn't possible anymore for those patches which have more then 78
characters on the first line.
The wrapping of the lines in the commit message will not be seen when
commiting but when rebasing via format-patch.
Was this the intention of this change or was my sort of workflow just
not in focus?
Any suggestion?
Stefan
--
Stefan-W. Hahn It is easy to make things.
It is hard to make things simple.
next reply other threads:[~2011-05-24 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 16:02 Stefan-W. Hahn [this message]
2011-05-24 16:27 ` commit a1f6baa5 (wrap long header lines) breaks my habit 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
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=20110524160253.GA7723@scotty.home \
--to=stefan.hahn@s-hahn.de \
--cc=git@vger.kernel.org \
/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).