all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: format hex numbers
Date: Sun, 31 Mar 2002 13:03:21 -0500	[thread overview]
Message-ID: <E16rjfl-0006Yp-00@fencepost.gnu.org> (raw)
In-Reply-To: <x5ofh46g1q.fsf@tupik.goethe.zz> (David.Kastrup@t-online.de)

> From: David.Kastrup@t-online.de (David Kastrup)
> Date: 31 Mar 2002 15:08:17 +0200
> 
> BTW, what is the difference in circulation between bug-gnu-emacs and
> emacs-pretest-bug?

In general, emacs-pretest-bug is only read by a small number of
active developers.

> The former is also gatewayed to gnu.emacs.bug,
> that much I know.  I am just trying to find out what bug should best
> be sent to which list.

It's best to send reports about unreleased versions (CVS and
pretests) to emacs-pretest-bug.  "M-x report-emacs-bug" will do that
automatically for you, btw.

> Are the lists and the progress on individual reports logged
> somewhere?

The lists are archived, although the archive for emacs-pretest-bug is
not publicly available (archives of bug-gnu-emacs are accessible via
mailman).

There's no bug-tracking system for Emacs.  It would be nice to have
one, but someone will have to volunteer to set up and maintain that.

  reply	other threads:[~2002-03-31 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27  8:50 format hex numbers Eli Barzilay
2002-03-31  5:06 ` Eli Zaretskii
2002-03-31 10:50   ` David Kastrup
2002-03-31 13:51     ` Eli Zaretskii
2002-03-31 13:08       ` David Kastrup
2002-03-31 18:03         ` Eli Zaretskii [this message]
2002-03-31 23:23     ` Eli Barzilay

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=E16rjfl-0006Yp-00@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=eliz@is.elta.co.il \
    /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.