From: Drew Adams <drew.adams@oracle.com>
To: Glenn Morris <rgm@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: RE: Why the change to *Messages*? [was: bug#15399...]
Date: Tue, 17 Sep 2013 15:26:02 -0700 (PDT) [thread overview]
Message-ID: <605e6426-ef58-42f0-a69e-4a4c0ff05710@default> (raw)
In-Reply-To: <78f5aafa-4e85-457a-8bfe-c3107b6a6925@default>
> > Ah, the expected "where was the discussion" email arrives on schedule.
> > The discussion is referenced in the commit message.
>
> Oh, wunderbar. In place of your sarcasm, why not post the commit
> message here, or provide a direct reference to the discussion?
> Why make people hunt for it?
>
> (FWIW, I can't even get to the ChangeLog file at
> http://bzr.savannah.gnu.org/lh/emacs/trunk/annotate/head:/src/ChangeLog?sort
> =date now, which is where the commit message is, I guess.
> It just times out. But I'll keep trying, unless you decide to be
> helpful and post the information here.)
OK, I finally got to it:
http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00135.html
And that is the same thread I referenced,from 3 years ago.
(Much of that thread does not show up here:
http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00078.html.
But even though the link it shows appears as already visited, the `Next
by thread' link, does add another message at the bottom of the page
(one at a time). Odd UI - you should be able to view another whole
page of the thread, not just one message at a time.)
prev parent reply other threads:[~2013-09-17 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4519DD53-A6F3-44DD-97C6-43443BBA1C98@mit.edu>
[not found] ` <jwva9jbxyrf.fsf-monnier+emacsbugs@gnu.org>
[not found] ` <592FE22C-6EA4-4F80-A19A-EBC88836B551@mit.edu>
[not found] ` <83y56vs3lj.fsf@fencepost.gnu.org>
2013-09-17 21:25 ` Why the change to *Messages*? [was: bug#15399...] Drew Adams
2013-09-17 21:36 ` Glenn Morris
2013-09-17 22:03 ` Drew Adams
2013-09-17 22:26 ` Drew Adams [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
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=605e6426-ef58-42f0-a69e-4a4c0ff05710@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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).