From: Eli Zaretskii <eliz@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: monnier@iro.umontreal.ca, ding@gnus.org, 10238@debbugs.gnu.org,
larsi@gnus.org
Subject: Re: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Tue, 24 Jan 2012 23:25:48 +0200 [thread overview]
Message-ID: <83pqe823oj.fsf@gnu.org> (raw)
In-Reply-To: <87pqe8kbg1.fsf@lifelogs.com>
> From: Ted Zlatanov <tzz@lifelogs.com>
> Date: Tue, 24 Jan 2012 16:00:46 -0600
> Cc: 10238@debbugs.gnu.org, Lars Magne Ingebrigtsen <larsi@gnus.org>
>
> SM> IOW, just make sure that if you only read the first 80 chars of
> SM> the first line, you get something meaningful that describes the bulk of
> SM> the patch.
>
> I'm OK with the above, as long as the Gnus developers are allowed to go
> over 80 in the first line within reason. So we'll keep the first line
> short, but if it has to go a little over 80, we'll make sure the really
> important stuff is at the very beginning.
I have yet to see a doc string whose first line could not be made less
than 80 characters. When in trouble, ask for help here, there are
enough native English speakers here who are proficient in making that
line clear, concise, and short.
next prev parent reply other threads:[~2012-01-24 21:25 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 [this message]
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
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=83pqe823oj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10238@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--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).