all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Frank Schmitt <ich@frank-schmitt.net>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Where's my bug report gone?
Date: Thu, 16 Oct 2008 10:28:41 +0200	[thread overview]
Message-ID: <m3abd5eyfa.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <n2skqx6mht.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu, 16 Oct 2008 03:13:34 -0400")

Glenn Morris <rgm@gnu.org> writes:

> Frank Schmitt wrote:
>
>> I just send a bug report to emacs-pretest-bug@gnu.org via M-x
>> report-emacs-bug in my Emacs 23 and really spend quite some time on this
>> trying to be as detailed as possible. But where is it?
>
> http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1174
>
> Didn't you get an automatic reply?

No, I didn't.

> It also appears on bug-gnu-emacs (yes, not emacs-pretest-bug):
>
> http://lists.gnu.org/archive/html/bug-gnu-emacs/2008-10/index.html

Ok. But why doesn't M-x report-emacs-bug send to bug-gnu-emacs then?

> Someone should reword the notice that is the last thing on
> emacs-pretest-bug:
>
> http://lists.gnu.org/archive/html/emacs-pretest-bug/2007-08/msg00066.html

Yes, it says that messages will go to emacs-devel there.

-- 
Have you ever considered how much text can fit in eighty columns?  Given that a
signature typically contains up to four lines of text, this space allows you to
attach a tremendous amount of valuable information to your messages.  Seize the
opportunity and don't waste your signature on bullshit that nobody cares about.




      reply	other threads:[~2008-10-16  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16  6:51 Where's my bug report gone? Frank Schmitt
2008-10-16  7:13 ` Glenn Morris
2008-10-16  8:28   ` Frank Schmitt [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3abd5eyfa.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    --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 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.