From: Tim Janik <timj@gnu.org>
To: git@vger.kernel.org
Subject: Overlong lines with git-merge --log
Date: Fri, 02 Nov 2012 02:30:15 +0100 [thread overview]
Message-ID: <50932227.3090401@gnu.org> (raw)
Hey all.
Using git-merge --log to merge commit messages that spawn multiple lines
will produce overlong summary lines.
That's because each summary line for a commit includes the entire commit
message (all lines concatenated).
According to git-fmt-merge-msg(1), --log should 'populate the log
message with one-line descriptions' instead of using the entire commit
messages.
Which would make a lot of sense, it's just not working as advertised.
Encountered with git version 1.7.9.5.
--
Yours sincerely,
Tim Janik
---
http://timj.testbit.eu/ - Free software Author
next reply other threads:[~2012-11-02 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 1:30 Tim Janik [this message]
2012-11-02 10:05 ` Overlong lines with git-merge --log Jeff King
2012-11-02 13:24 ` Tim Janik
2012-11-02 13:49 ` Stephen Bash
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=50932227.3090401@gnu.org \
--to=timj@gnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.