From: "Eli Zaretskii" <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: emacs-pretest-bug (Was: [bug] line move and truncation)
Date: Tue, 16 Nov 2004 23:06:10 +0200 [thread overview]
Message-ID: <01c4cc20$Blat.v2.2.2$3e85ea80@zahav.net.il> (raw)
In-Reply-To: <87hdnp22eb.fsf_-_@jurta.org> (message from Juri Linkov on Tue, 16 Nov 2004 18:18:36 +0200)
> From: Juri Linkov <juri@jurta.org>
> Date: Tue, 16 Nov 2004 18:18:36 +0200
>
> > BTW, who is monitoring emacs-pretest-bug?
>
> This is a serious problem. It seems many Emacs developers are not
> subscribed to emacs-pretest-bug. That might explain why some bugs
> remain unfixed.
And what prevents you from subscribing to emacs-pretest-bug? It's a
public list, AFAIK.
> 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.
The fact that some people report bugs on emacs-devel IMHO means
nothing except that those people wrote to the wrong address. But
since all those who subscribe to emacs-pretest-bug also read
emacs-devel, we don't usually tell such people to take the thread to
emacs-pretest-bug.
next prev parent reply other threads:[~2004-11-16 21:06 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 [this message]
2004-11-16 23:12 ` Miles Bader
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='01c4cc20$Blat.v2.2.2$3e85ea80@zahav.net.il' \
--to=eliz@gnu.org \
--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).