From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 10238@debbugs.gnu.org
Cc: tzz@lifelogs.com, schwab@linux-m68k.org, ding@gnus.org
Subject: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Mon, 30 Jan 2012 20:46:06 -0500 [thread overview]
Message-ID: <jwvfwewodf0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87ehugajy7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 30 Jan 2012 23:45:20 +0100")
>> I think we should try to keep it under 80, and if it has to go over, the
>> essential information should be before the 80th char. But forcing it to
>> 80 will force us to write convoluted summaries that misrepresent the
>> commit for the sake of saving a few characters.
> I think it's fine for the summary line to not describe the entire patch.
Actually, the way to think about this is that this "summary" is really
about giving a *name* to the patch. In this context, 80chars is usually
not that restrictive (although often a large part is taken by some kind
of context like "lisp/emacs-lisp/tabulated-list.el: ", that still leaves
40chars for the "name-in-context").
Stefan
prev parent reply other threads:[~2012-01-31 1:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvpqg1cskp.fsf-monnier+@gnu.org>
[not found] ` <m3sjjvnpw4.fsf@stories.gnus.org>
[not found] ` <jwvvcorymdh.fsf-monnier+INBOX@gnu.org>
2012-01-24 22:00 ` Ted Zlatanov
2012-01-24 21:25 ` Eli Zaretskii
2012-01-24 22:34 ` Ted Zlatanov
2012-01-24 23:02 ` Andreas Schwab
2012-01-25 6:30 ` Eli Zaretskii
2012-01-25 15:00 ` Ted Zlatanov
2012-01-25 22:56 ` Lars Ingebrigtsen
2012-01-26 15:34 ` Ted Zlatanov
2012-01-30 22:45 ` Lars Ingebrigtsen
2012-01-31 1:46 ` Stefan Monnier [this message]
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=jwvfwewodf0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=10238@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=schwab@linux-m68k.org \
--cc=tzz@lifelogs.com \
/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 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 NNTP newsgroup(s).