From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: Nonempty second line in commit message (??)
Date: Sun, 29 Mar 2015 11:10:18 +0000 [thread overview]
Message-ID: <871tk8ukit.fsf@violet.siamics.net> (raw)
In-Reply-To: <jwv4mp4jvss.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 29 Mar 2015 00:05:22 -0400")
>>>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> While commiting I got this error: "Nonempty second line in commit
>> message".
>> Why can't the second line be non-empty?
> Git considers "the summary" (displayed in short logs and things like
> that) to be the concatenation of all lines until the first empty
> line. I think this convention sucks (if you forget such an empty
> line, it leads to ridiculously long "summaries",
That’s just “the summary is the first paragraph of the entry”
rule. One could certainly screw up with this convention in
place, but that’s also possible with any other convention.
> and it forces the addition of an empty line at a spot where you don't
> always want one).
Any examples for this point?
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-03-29 11:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 22:09 Nonempty second line in commit message (??) Jan D.
2015-03-28 22:27 ` Ivan Shmakov
2015-03-28 23:33 ` Paul Eggert
2015-03-29 7:45 ` Jan D.
2015-03-29 20:10 ` Paul Eggert
2015-03-29 4:05 ` Stefan Monnier
2015-03-29 11:10 ` Ivan Shmakov [this message]
2015-03-29 20:54 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tk8ukit.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).