unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: bug tracker down again?
Date: Tue, 05 Jan 2010 07:17:49 -0700	[thread overview]
Message-ID: <87aawsmy9e.fsf@stupidchicken.com> (raw)
In-Reply-To: <A7D7EACA06E4446E817D73971E12008B@us.oracle.com> (Drew Adams's message of "Mon, 4 Jan 2010 09:57:45 -0800")

"Drew Adams" <drew.adams@oracle.com> writes:

> I sent two new bug reports to 'emacs-pretest-bug@gnu.org' yesterday. Neither has
> shown up, apparently. I got no email from the bug tracker, and they still
> haven't show up at http://debbugs.gnu.org/.
>
> 'emacs-pretest-bug@gnu.org' is the address that comes up automatically via
> `report-emacs-bug', at least in the Windows binary I got from
> http://alpha.gnu.org/gnu/emacs/pretest/windows/.
>
> And I was able to successfully send a different pretest bug report (#5299) to it
> previously. But it no longer seems to work.
>
> The two reports I sent contained attachments - dunno if that is significant.
> Also, as bug #5299 reports, there is a bug in `report-emacs-bug' itself that
> requires me to create the mail messages by hand in my mail client. But I doubt
> that that is related. I created the missing bug reports the same way as the
> successful report #5299.

The submission list for the bug tracker is moderated, so it takes some
time for emails to hit the tracker.  In particular, large attachments
are always flagged for moderation.

We currently lack enough moderators, so anyone who is interested in
helping to moderate, please email me.




  reply	other threads:[~2010-01-05 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 17:57 bug tracker down again? Drew Adams
2010-01-05 14:17 ` Chong Yidong [this message]
2010-01-06  0:23 ` Glenn Morris
2010-01-07 16:34   ` Drew Adams

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=87aawsmy9e.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=drew.adams@oracle.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).