From: Jonny Grant <jg@jguk.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: simark@simark.ca, gdb@sourceware.org
Subject: Re: http://mail.gnu.org/mailman/listinfo/bug-gdb/ down
Date: Sat, 30 May 2020 01:20:02 +0100 [thread overview]
Message-ID: <f62a9ddf-8883-7180-cbb3-ff22291a21d9@jguk.org> (raw)
In-Reply-To: <83eer4sgi1.fsf@gnu.org>
On 28/05/2020 07:47, Eli Zaretskii wrote:
>> From: Jonny Grant <jg@jguk.org>
>> Date: Wed, 27 May 2020 23:26:26 +0100
>>
>> My apologies, correct version of the patch attached.
>
> What was wrong with the previous version, and why this one is better?
> I'm probably missing something, but it sounds to me like an explicit
> 'mailto:' is better?
>
Hello Eli
My apologies, the first version didn't compile as you mentioned in your other email.
Other shell tools with such URLs or email addresses are using <> without the mailto:, eg make --help
Report bugs to <bug-make@gnu.org>
gdb --help currently has extra quotes:-
Report bugs to "<http://www.gnu.org/software/gdb/bugs/>".
I had kept the same style with the quotes. Would it actually be better to remove the quotes so it matches other tools
like strings --help etc?
So it would then look like:
Report bugs to <http://www.gnu.org/software/gdb/bugs/>.
GDB mailing list <gdb@sourceware.org>
Thanks, Jonny
next prev parent reply other threads:[~2020-05-30 0:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 11:07 Jonny Grant
2020-05-26 14:17 ` Simon Marchi
2020-05-27 22:12 ` Jonny Grant
2020-05-27 22:26 ` Jonny Grant
2020-05-28 6:47 ` Eli Zaretskii
2020-05-30 0:20 ` Jonny Grant [this message]
2020-05-30 6:19 ` Eli Zaretskii
2020-06-27 19:37 ` Jonny Grant
2020-06-28 1:27 ` Joel Brobecker
2020-06-28 5:20 ` Andreas Schwab
2020-06-28 15:26 ` Jonny Grant
2020-06-28 15:36 ` Joel Brobecker
2020-06-29 11:44 ` Pedro Alves
2020-06-29 17:48 ` Joel Brobecker
2020-07-06 18:54 ` Joel Brobecker
2020-07-08 22:03 ` Jonny Grant
2020-06-28 15:21 ` Jonny Grant
2020-05-28 6:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f62a9ddf-8883-7180-cbb3-ff22291a21d9@jguk.org \
--to=jg@jguk.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=simark@simark.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox