From: Andreas Schwab <schwab@linux-m68k.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs] lists: Fix thinko
Date: Wed, 02 Jun 2021 10:25:34 +0200 [thread overview]
Message-ID: <87bl8on05d.fsf@igel.home> (raw)
In-Reply-To: <890401b1dfb48c33723980b7a0b30419315ff8ab.1622584049.git.segher@kernel.crashing.org> (Segher Boessenkool's message of "Tue, 1 Jun 2021 21:49:28 +0000")
On Jun 01 2021, Segher Boessenkool wrote:
> diff --git a/htdocs/lists.html b/htdocs/lists.html
> index 4ac5d5a84cd1..e9636198b732 100644
> --- a/htdocs/lists.html
> +++ b/htdocs/lists.html
> @@ -226,7 +226,7 @@ our lists into a single folder named INLIST.gcc:</p>
>
> <blockquote><p><code>
> :0<br />
> -* ^List-Id: .*<.*@gcc.gnu.org>$<br />
> +* ^List-Id: .*<.*.gcc.gnu.org>$<br />
Shouldn't the < and > be mangled as < and >?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-06-02 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 21:49 Segher Boessenkool
2021-06-02 7:17 ` Gerald Pfeifer
2021-06-02 16:27 ` Segher Boessenkool
2021-06-02 8:25 ` Andreas Schwab [this message]
2021-06-02 16:27 ` Segher Boessenkool
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=87bl8on05d.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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.
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).