From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: bug bugs [was Re: ^M in the info files]
Date: Mon, 12 Jan 2009 23:24:35 -0500 [thread overview]
Message-ID: <s3wsczsuik.fsf_-_@fencepost.gnu.org> (raw)
In-Reply-To: <uy6xfc0rw.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Jan 2009 06:01:23 +0200")
Eli Zaretskii wrote:
> Why won't the tracker get its act together and stop forcing us into
> editing mail headers?
It's been asked for repeatedly, but it doesn't happen. There seems no
point even discussing it, all the points have been made.
I know people shouldn't have to make this effort with headers, but I
was only asking. I'm fed up of duplicate and triplicate mails, and
large numbers of bogus bug reports that need merging.
> I use the Rmail's `r' command, which replies to all the original
> "To" and "CC" addressees.
I don't use rmail, but rmail-dont-reply-to-names ...?
next prev parent reply other threads:[~2009-01-13 4:24 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 11:09 A few bugs not in the bug tracker (I think) Juanma Barranquero
2008-08-06 12:31 ` Kenichi Handa
2008-08-06 13:14 ` Juanma Barranquero
2008-08-06 13:36 ` Juanma Barranquero
2008-08-07 4:25 ` Miles Bader
2008-08-07 11:26 ` Juanma Barranquero
2008-08-07 0:48 ` ^M in the info files Kenichi Handa
2008-08-07 3:20 ` Eli Zaretskii
2008-08-07 3:22 ` Juanma Barranquero
2008-08-07 3:47 ` Kenichi Handa
2008-08-07 13:01 ` Juanma Barranquero
2008-08-08 1:28 ` Kenichi Handa
2008-08-08 11:02 ` Juanma Barranquero
2008-08-13 10:08 ` Kenichi Handa
2008-08-15 23:09 ` Juanma Barranquero
2008-08-07 20:18 ` Stefan Monnier
2008-11-28 21:28 ` Drew Adams
2008-11-28 22:39 ` Eli Zaretskii
2008-11-28 22:44 ` Juanma Barranquero
2008-11-29 10:50 ` Eli Zaretskii
2008-11-29 11:56 ` Juanma Barranquero
2008-11-28 22:49 ` Drew Adams
2008-11-29 10:51 ` Eli Zaretskii
2009-01-10 11:15 ` Eli Zaretskii
2009-01-10 12:14 ` Eli Zaretskii
2009-01-12 20:56 ` Stefan Monnier
2009-01-12 22:04 ` Eli Zaretskii
2009-01-10 14:07 ` Juanma Barranquero
2009-01-10 15:13 ` Eli Zaretskii
2009-01-10 18:23 ` Juanma Barranquero
2009-01-10 19:08 ` Eli Zaretskii
2009-01-10 19:12 ` Eli Zaretskii
2009-01-10 19:19 ` Eli Zaretskii
2009-01-10 21:04 ` Juanma Barranquero
2009-01-10 16:21 ` Drew Adams
2009-01-10 23:16 ` Lennart Borgman
2009-01-11 5:41 ` dhruva
2009-01-11 5:51 ` dhruva
2009-01-12 20:54 ` Stefan Monnier
2009-01-12 22:13 ` Eli Zaretskii
2009-01-12 22:27 ` Glenn Morris
2009-01-13 4:01 ` Eli Zaretskii
2009-01-13 4:24 ` Glenn Morris [this message]
2009-01-13 18:56 ` bug bugs [was Re: ^M in the info files] Eli Zaretskii
2009-01-13 20:50 ` bug bugs Glenn Morris
2009-01-14 4:12 ` Eli Zaretskii
2009-01-14 13:45 ` Chong Yidong
2009-01-14 19:13 ` Eli Zaretskii
2009-01-15 0:30 ` Stephen J. Turnbull
2009-01-14 19:40 ` Glenn Morris
2008-08-06 18:04 ` A few bugs not in the bug tracker (I think) Eli Zaretskii
2008-08-06 13:35 ` Don Armstrong
2008-08-06 13:38 ` Juanma Barranquero
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=s3wsczsuik.fsf_-_@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).