From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 10238@debbugs.gnu.org, tzz@lifelogs.com, larsi@gnus.org, ding@gnus.org
Subject: bug#10238: R in gnus-summary does not pop a frame like F does
Date: Wed, 25 Jan 2012 01:30:49 -0500 [thread overview]
Message-ID: <E1RpwNd-0008Fp-W0@fencepost.gnu.org> (raw)
In-Reply-To: <m2hazk4scx.fsf@igel.home> (message from Andreas Schwab on Wed, 25 Jan 2012 00:02:06 +0100)
> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, 10238@debbugs.gnu.org, larsi@gnus.org, ding@gnus.org
> Date: Wed, 25 Jan 2012 00:02:06 +0100
>
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
> > 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.
>
> The summary line doesn't need to be precise. It should just give an
> informal overview of the change.
100% agreement.
next prev parent reply other threads:[~2012-01-25 6:30 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 [this message]
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=E1RpwNd-0008Fp-W0@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=10238@debbugs.gnu.org \
--cc=ding@gnus.org \
--cc=larsi@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).