unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-diffs emails can get long subject if log starts with "*"
Date: Mon, 24 Nov 2014 12:12:42 -0500	[thread overview]
Message-ID: <pfzjbgzfn9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 1573504.ME31ScXqvn@descartes

Rüdiger Sonderfeld wrote:

>> Also seems dumb to me to ignore line-breaks, and insist on paragrpah
>> breaks, but whatever.
>
> That's why the recommendation for git is to limit the first line to 50 
> characters. 

"First line summarizes the commit" is fine by me. What I find dumb is
the requirement for that first line to be followed by a blank line, not
a new line.

Because
who
needs
to
write
50
characters
like
this?

For example, just now I wanted to use a commit log which was about 1.5
lines long in total, but had a natural break (for a comma) at the end of
the first line. Rather than rewrite it as "1 + blank + 1.5 lines", I
simply dropped the last half line.

If a newline marked the end of the summary/title/whatever, then
log --oneline (and emacs-diffs subjects) would look fine, with no action
needed.

But obviously it isn't going to change, so we need to learn new habits,
and write little tools to enforce said habits.



  parent reply	other threads:[~2014-11-24 17:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-22 22:31 emacs-diffs emails can get long subject if log starts with "*" Glenn Morris
2014-11-22 22:58 ` Andreas Schwab
2014-11-22 23:06   ` Glenn Morris
2014-11-23  0:13     ` Glenn Morris
2014-11-23  0:24       ` Glenn Morris
2014-11-23  0:46     ` Paul Eggert
2014-11-23  4:44     ` Yuri Khan
2014-11-23 10:15       ` Thien-Thi Nguyen
2014-11-23 16:06       ` Eli Zaretskii
2014-11-23 23:28         ` Richard Stallman
2014-11-23 16:04     ` Rüdiger Sonderfeld
2014-11-23 17:26       ` Eli Zaretskii
2014-11-24 17:12       ` Glenn Morris [this message]
2014-11-24 17:23         ` Andreas Schwab
2014-11-24 17:49   ` Stefan Monnier
2014-11-24 18:06     ` Andreas Schwab

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=pfzjbgzfn9.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ruediger@c-plusplus.de \
    /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).