unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Rüdiger Sonderfeld" <ruediger@c-plusplus.de>
To: emacs-devel@gnu.org
Cc: Andreas Schwab <schwab@linux-m68k.org>
Subject: Re: emacs-diffs emails can get long subject if log starts with "*"
Date: Sun, 23 Nov 2014 17:04:36 +0100	[thread overview]
Message-ID: <1573504.ME31ScXqvn@descartes> (raw)
In-Reply-To: <iolhn2rg2g.fsf@fencepost.gnu.org>

On Saturday 22 November 2014 18:06:15 Glenn Morris wrote:
> Seems dumb to me for a thing that sends out mails not to include a check
> on subject length, so I'll probably attempt to patch that in.
> 
> 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.  This of course conflicts with the common practice in Emacs to 
simply use the ChangeLog entry as the commit message.  I personally try to 
write the commit messages in a git-friendly format and append the ChangeLog 
entry (if it is necessary) as its own paragraph.  I would suggest to make this 
common practice to improve the compatibility with the existing git tools.  But 
of course we can't got back and change all of the history to confirm.

btw. there is a git-commit-mode (used by magit), which checks for this rule.

Regards,
Rüdiger




  parent reply	other threads:[~2014-11-23 16:04 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 [this message]
2014-11-23 17:26       ` Eli Zaretskii
2014-11-24 17:12       ` Glenn Morris
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=1573504.ME31ScXqvn@descartes \
    --to=ruediger@c-plusplus.de \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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).