From: Miles Bader <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>, emacs-devel@gnu.org
Subject: Re: emacs-pretest-bug (Was: [bug] line move and truncation)
Date: Tue, 16 Nov 2004 18:12:01 -0500 [thread overview]
Message-ID: <20041116231201.GA23221@fencepost> (raw)
In-Reply-To: <01c4cc20$Blat.v2.2.2$3e85ea80@zahav.net.il>
On Tue, Nov 16, 2004 at 11:06:10PM +0200, Eli Zaretskii wrote:
> > So really emacs-pretest-bug looks like a part of emacs-devel
> > "hidden" from many Emacs developers. This hampers the development.
> > A good solution is to declare emacs-pretest-bug obsolete and to
> > change the value of `report-emacs-bug-pretest-address' to
> > "emacs-devel@gnu.org".
>
> No. emacs-devel is for _discussions_about_ Emacs development, while
> emacs-pretest-bug is for reporting bugs and related discussions, and
> only for that. Therefore, people who read emacs-pretest-bug should be
> those who are interested in working on fixing bugs, not simply have
> some interest in Emacs development.
This seems like a rather bizarre justification.... surely the _vast_ majority
of people who read emacs-devel are interested in fixing bugs.
As far as I can see, emacs-pretest-bug is already effectively obsoleted by
emacs-devel, but still gets a few random postings because of the way emacs is
configured, and out of habit by a few long-term hackers and pretesters.
It would be much less confusing to just redirect emacs-pretest-bug to
emacs-devel and be done with it.
-Miles
--
"Suppose He doesn't give a shit? Suppose there is a God but He
just doesn't give a shit?" [George Carlin]
next prev parent reply other threads:[~2004-11-16 23:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 8:56 [bug] line move and truncation Lars Hansen
2004-11-16 14:03 ` Kim F. Storm
2004-11-16 14:08 ` Lars Hansen
2004-11-16 16:18 ` emacs-pretest-bug (Was: [bug] line move and truncation) Juri Linkov
2004-11-16 21:06 ` Eli Zaretskii
2004-11-16 23:12 ` Miles Bader [this message]
2004-11-17 4:53 ` Eli Zaretskii
2004-11-17 5:02 ` Richard Stallman
2004-11-16 14:19 ` [bug] line move and truncation Kim F. Storm
2004-11-16 17:50 ` Lars Hansen
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=20041116231201.GA23221@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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).