unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Don Armstrong <don@donarmstrong.com>
To: emacs-devel@gnu.org, 21@emacsbugs.donarmstrong.com
Subject: bug#21: Scrolling occasionally stops in *compilation*
Date: Wed, 11 Jun 2008 11:50:31 -0700	[thread overview]
Message-ID: <20080611185031.GA17024__3980.92551990903$1213211301$gmane$org@archimedes.ucr.edu> (raw)
In-Reply-To: <E1K6UOO-00058f-43@fencepost.gnu.org>

On Wed, 11 Jun 2008, Richard M Stallman wrote:
>     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.
> 
> That is a pain in the neck for everyone on bug-gnu-emacs.

In what way?

> It should be cc'd to emacs-bug-tracker instead.

This is an example of a message which would have normally just been
sent to bug-gnu-emacs anyway. Think of nnn@emacsbugs.donarmstrong.com
as just an alias for bug-gnu-emacs in the case where nnn is a bug is
in the emacs package.

>     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.
> 
> I don't see anything bad about it.
> Would you like to try to substantiate that statement?

If the messages don't go through the bug tracker before they hit
bug-gnu-emacs, you'd have no clue what bug is being discussed, nor
where to look to see the followup information, and you additionally
have to be subscribed to some other mailing list to get any
information about the bug at all.

We can easily stop sending all messages to bug-gnu-emacs if we want
to, but then no messages would go to bug-gnu-emacs at all, not even
the ones that were originally sent there.

From what I see, the primary issue is one of the bugs not being
threaded properly, which Stefan already raised with me, and is
http://bugs.debian.org/485697


Don Armstrong

-- 
I leave the show floor, but not before a pack of caffeinated Jolt gum
is thrust at me by a hyperactive girl screaming, "Chew more! Do more!"
The American will to consume more and produce more personified in a
stick of gum. I grab it.
 -- Chad Dickerson

http://www.donarmstrong.com              http://rzlab.ucr.edu





  reply	other threads:[~2008-06-11 18:50 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
2008-06-11 17:45     ` Richard M Stallman
2008-06-11 18:50       ` Don Armstrong [this message]
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='20080611185031.GA17024__3980.92551990903$1213211301$gmane$org@archimedes.ucr.edu' \
    --to=don@donarmstrong.com \
    --cc=21@emacsbugs.donarmstrong.com \
    --cc=emacs-devel@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).