From: Juri Linkov <juri@jurta.org>
Subject: emacs-pretest-bug (Was: [bug] line move and truncation)
Date: Tue, 16 Nov 2004 18:18:36 +0200 [thread overview]
Message-ID: <87hdnp22eb.fsf_-_@jurta.org> (raw)
In-Reply-To: <419A09C9.3060308@math.ku.dk> (Lars Hansen's message of "Tue, 16 Nov 2004 15:08:09 +0100")
Lars Hansen <larsh@math.ku.dk> writes:
> Kim F. Storm wrote:
>>I just posted an analysis of the problem to emacs-pretest-bug ...
>
> Thanks.
> 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. Also often bug reports results in discussions that
should belong to emacs-devel, and where unsubscribed Emacs developers
can't participate. And often developers report bugs on emacs-devel,
(perhaps anticipating a possible discussion). 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".
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-11-16 16:18 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 ` Juri Linkov [this message]
2004-11-16 21:06 ` emacs-pretest-bug (Was: [bug] line move and truncation) Eli Zaretskii
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=87hdnp22eb.fsf_-_@jurta.org \
--to=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).