all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10238@debbugs.gnu.org, larsi@gnus.org, ding@gnus.org
Subject: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Tue, 24 Jan 2012 16:34:42 -0600	[thread overview]
Message-ID: <87vco0ivb1.fsf__47911.0014428899$1327440955$gmane$org@lifelogs.com> (raw)
In-Reply-To: <83pqe823oj.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 24 Jan 2012 23:25:48 +0200")

On Tue, 24 Jan 2012 23:25:48 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 

>> 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.

EZ> I have yet to see a doc string whose first line could not be made less
EZ> than 80 characters.  When in trouble, ask for help here, there are
EZ> enough native English speakers here who are proficient in making that
EZ> line clear, concise, and short.

We're talking about VCS commit messages, not docstrings.  It's a
different context, and for VCS commits often there is information that
needs to be distilled into that first line and 80 chars are not enough.

Ted





  parent reply	other threads:[~2012-01-24 22:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 21:20 bug#10238: R in gnus-summary does not pop a frame like F does Stefan Monnier
2012-01-04 21:01 ` Lars Magne Ingebrigtsen
2012-01-05  1:26   ` Stefan Monnier
2012-01-05  5:01     ` Lars Magne Ingebrigtsen
2012-01-05 21:47       ` Stefan Monnier
2012-01-06  3:19         ` Lars Magne Ingebrigtsen
     [not found]     ` <87pqe8kbg1.fsf@lifelogs.com>
2012-01-24 21:25       ` Eli Zaretskii
     [not found]       ` <83pqe823oj.fsf@gnu.org>
2012-01-24 22:34         ` Ted Zlatanov [this message]
     [not found]         ` <87vco0ivb1.fsf@lifelogs.com>
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
2012-01-24 22:00     ` Ted Zlatanov

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='87vco0ivb1.fsf__47911.0014428899$1327440955$gmane$org@lifelogs.com' \
    --to=tzz@lifelogs.com \
    --cc=10238@debbugs.gnu.org \
    --cc=ding@gnus.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.