From: Ivan Shmakov <ivan@siamics.net>
To: emacs-devel@gnu.org
Subject: Re: Nonempty second line in commit message (??)
Date: Sat, 28 Mar 2015 22:27:42 +0000 [thread overview]
Message-ID: <87619kvjtt.fsf@violet.siamics.net> (raw)
In-Reply-To: <ED152E86-F3AF-4C70-AE0C-6F9C83691874@swipnet.se> (Jan D.'s message of "Sat, 28 Mar 2015 23:09:17 +0100")
>>>>> Jan D <jan.h.d@swipnet.se> writes:
> While commiting I got this error:
> "Nonempty second line in commit message".
> Why can't the second line be non-empty? Are commit message limitied
> to one line now? Or must the second be empty and then the rest be
> non-empty?
Yes.
The first line is reserved for the summary, which should be a
/concise/ overall description of the change. For one thing, it
should deliver the essence of the change even if you’re reading
through emacs-diffs@ /and/ the messages there are listed
one-per-line (assuming the 80 CPL IBM standard.)
Naturally, such summary should never be long enough to warrant a
second (or third, or…) line.
The summary forms a paragraph on its own, so the usual
ChangeLog-style details should follow after a customary
“paragraph break” empty line.
> Or is the error message just extraordinary bad?
--
FSF associate member #7257 http://boycottsystemd.org/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2015-03-28 22:27 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 [this message]
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
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=87619kvjtt.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).