From: Mike Hommey <mh@glandium.org>
To: git@vger.kernel.org
Subject: commit summary, --pretty=short and other tools
Date: Mon, 17 Sep 2007 13:21:36 +0200 [thread overview]
Message-ID: <20070917112136.GA30201@glandium.org> (raw)
Hi,
I kind of shot myself in the foot with how to type proper commit
messages.
The git-commit manual page reads:
Though not required, it´s a good idea to begin the commit message with a
single short (less than 50 character) line summarizing the change,
followed by a blank line and then a more thorough description.
... and I happen to not have done the "followed by a blank line" part.
Now, git log --pretty=oneline (for instance), shows me the full commit
message on one line, which is not really what I would expect...
On the other hand, and that's how I got trapped into this, gitweb and
gitk only display the first line, be it followed by a blank line or not.
So, IMHO, there would be 2 solutions:
- either change --pretty=oneline,short and other similar things to take
only the first line and change the git-commit manpage (and whenever
else this might be written)
- or change gitweb, gitk and any other tool that would only take the
first line so that it takes the same summary as --pretty=oneline.
What do you think ?
Mike
next reply other threads:[~2007-09-17 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 11:21 Mike Hommey [this message]
2007-09-17 11:42 ` commit summary, --pretty=short and other tools Jeff King
2007-09-17 23:52 ` Benoit SIGOURE
2007-09-18 0:24 ` Junio C Hamano
2007-09-18 7:19 ` Andreas Ericsson
2007-09-18 10:13 ` Johannes Schindelin
2007-09-18 10:23 ` Andreas Ericsson
2007-09-18 10:27 ` Benoit SIGOURE
2007-09-18 10:54 ` Johannes Schindelin
2007-09-18 11:43 ` Wincent Colaiuta
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=20070917112136.GA30201@glandium.org \
--to=mh@glandium.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.