From: Nick Roberts <nickrob@snap.net.nz>
To: emacs-devel@gnu.org
Subject: emacs-pretest-bug
Date: Thu, 31 Jan 2008 21:22:24 +1300 [thread overview]
Message-ID: <18337.34112.788356.568329@kahikatea.snap.net.nz> (raw)
Now that emacs-pretest-bug is just an alias for emacs-devel and no longer
archived, how about the following changes to avoid confusion and discourage
crossposting?
--
Nick http://www.inet.net.nz/~nickrob
*** emacsbug.el.~1.58.6.20.~ 2008-01-13 01:01:18.000000000 +1300
--- emacsbug.el 2008-01-31 21:19:30.000000000 +1300
***************
*** 48,54 ****
:group 'emacsbug
:type 'string)
! (defcustom report-emacs-bug-pretest-address "emacs-pretest-bug@gnu.org"
"*Address of mailing list for GNU Emacs pretest bugs."
:group 'emacsbug
:type 'string)
--- 48,54 ----
:group 'emacsbug
:type 'string)
! (defcustom report-emacs-bug-pretest-address "emacs-devel@gnu.org"
"*Address of mailing list for GNU Emacs pretest bugs."
:group 'emacsbug
:type 'string)
*** trouble.texi.~1.64.2.2.~ 2008-01-10 23:18:50.000000000 +1300
--- trouble.texi 2008-01-31 21:13:17.000000000 +1300
*************** well.
*** 551,557 ****
@cindex reporting bugs
The best way to send a bug report is to mail it electronically to the
Emacs maintainers at @email{bug-gnu-emacs@@gnu.org}, or to
! @email{emacs-pretest-bug@@gnu.org} if you are pretesting an Emacs beta
release. (If you want to suggest a change as an improvement, use the
same address.)
--- 551,557 ----
@cindex reporting bugs
The best way to send a bug report is to mail it electronically to the
Emacs maintainers at @email{bug-gnu-emacs@@gnu.org}, or to
! @email{emacs-devel@@gnu.org} if you are pretesting an Emacs beta
release. (If you want to suggest a change as an improvement, use the
same address.)
next reply other threads:[~2008-01-31 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 8:22 Nick Roberts [this message]
2008-01-31 9:44 ` emacs-pretest-bug Jason Rumney
2008-02-01 6:34 ` emacs-pretest-bug Richard Stallman
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=18337.34112.788356.568329@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--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 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.