From: Eli Zaretskii <eliz@gnu.org>
To: myglc2 <myglc2@gmail.com>
Cc: 29290@debbugs.gnu.org
Subject: bug#29290: 25.3; bug-gnu-emacs archive web search fails to find matching bugs
Date: Wed, 15 Nov 2017 05:34:13 +0200 [thread overview]
Message-ID: <83fu9gjjuy.fsf@gnu.org> (raw)
In-Reply-To: <86bmk4pp9d.fsf@gmail.com> (message from myglc2 on Tue, 14 Nov 2017 15:41:02 -0500)
> From: myglc2 <myglc2@gmail.com>
> Cc: 29290@debbugs.gnu.org
> Date: Tue, 14 Nov 2017 15:41:02 -0500
>
> #23576: Re: bug#23576: [documentation] =?utf-8?Q?=E2=80=98Using?= Emacs
That's not "garbled", that's the RFC 2047 encoded subject line, as
originally produced by the MUA of the person who reported the bug.
> I call this "garbled" because it is so mangled by escape that the title
> is uninformative and the paragraph is unreadable.
You should look at the highlighted matches for the search strings, and
determine whether this is what you are looking for.
> Am I being too harsh? ;-)
Definitely.
> Please look for the links on https://debbugs.gnu.org/ with "emacs" in
> their title.
>
> You will see links to ...
>
> 1) https://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
>
> 2) https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs;max-bugs=100;base-order=1;bug-rev=1
>
> These send your emacs users with bugs to report to places that you don't
> recommend that they go so I am saying please change them ...
I see no reason to change that.
next prev parent reply other threads:[~2017-11-15 3:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-1252961@rt.gnu.org>
2017-11-13 23:17 ` bug#29290: 25.3; bug-gnu-emacs archive web search fails to find matching bugs myglc2
2017-11-13 23:45 ` Glenn Morris
2017-11-14 0:12 ` myglc2
2017-11-14 21:15 ` Bob Proulx
2017-11-14 22:02 ` Ian Kelling
2017-11-14 22:30 ` Glenn Morris
2017-11-30 17:15 ` bug#29290: [gnu.org #1252961] " Ian Kelling via RT
2017-11-14 15:18 ` Eli Zaretskii
2017-11-14 17:42 ` myglc2
2017-11-14 18:53 ` Eli Zaretskii
2017-11-14 20:41 ` myglc2
2017-11-15 3:34 ` Eli Zaretskii [this message]
2017-11-15 11:47 ` Noam Postavsky
2017-11-15 17:44 ` Eli Zaretskii
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=83fu9gjjuy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29290@debbugs.gnu.org \
--cc=myglc2@gmail.com \
/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).