unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Joe Wells'" <jbw@macs.hw.ac.uk>
Cc: bug-gnu-emacs@gnu.org,
	'Stefan Monnier' <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: RE: bug#21: Scrolling occasionally stops in *compilation*
Date: Wed, 11 Jun 2008 06:28:32 -0700	[thread overview]
Message-ID: <00d601c8cbc7$0b96ecf0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <86prqofey8.fsf@macs.hw.ac.uk>

> > I think this is the kind of thing Richard was trying to say 
> should not be sent
> > to the entire universe.
> >
> > This mail, like many others that are similar, means nothing 
> to me. I didn't file
> > this bug. I wasn't even aware of it. I'm still not aware of 
> it, by mail - except
> > for this cryptic message.
> >
> > Please try to focus the send list for this kind of thing.
> 
> Any e-mail sent to XYZ@emacsbugs.donarmstrong.com (where XYZ is the
> bug number) will be CC-ed to bug-gnu-emacs automatically.  This is
> what Stefan did.
> 
> Stefan could have sent this e-mail privately, but then it would not be
> recorded as part of the bug report's log, which would be bad.
> 
> It is good that e-mail sent to XYZ@emacsbugs.donarmstrong.com is CC-ed
> to bug-gnu-emacs automatically.  Simply turning this off would be bad.
> 
> There is no simple solution, although there may be a complicated one.

Good explanation. Unfortunate situation.

It took me a while, searching through all of the mail copies I kept, to see if
this wasn't perhaps a bug I had filed. There is nothing in Stefan's reply mail
to indicate who reported the bug or when it was reported - just an oblique
reference to "your problem". 

Not to mention that it is not enough to sort by Subject, since "Scrolling..."
collates differently from "bug#21: Scrolling...".

Anyway, the bug logging is a plus, even if it is still quite primitive.





  reply	other threads:[~2008-06-11 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:02 bug#21: Scrolling occasionally stops in *compilation* Stefan Monnier
2008-06-10 19:47 ` Drew Adams
     [not found] ` <mailman.13010.1213128432.18990.bug-gnu-emacs@gnu.org>
2008-06-11 10:23   ` Joe Wells
2008-06-11 13:28     ` Drew Adams [this message]
2008-06-11 17:45     ` Richard M Stallman
2008-06-11 18:50       ` Don Armstrong
2008-06-11 19:14       ` which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Joe Wells
2008-06-11 21:42         ` which bug messages should be sent where? Jason Rumney
2008-06-15 17:55         ` bug#388: which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Richard M Stallman
2010-03-17 16:12 ` bug#21: Scrolling occasionally stops in *compilation* Glenn Morris

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='00d601c8cbc7$0b96ecf0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jbw@macs.hw.ac.uk \
    --cc=monnier@iro.umontreal.ca \
    /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).