From: FX <fxcoudert@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Mike Stump <mikestump@comcast.net>, gcc-patches@gcc.gnu.org
Subject: Re: Web page for binaries
Date: Sat, 27 May 2017 09:33:00 -0000 [thread overview]
Message-ID: <5121AC76-CA60-475A-B5D2-DEA224E9212A@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1705252216300.3529@anthias.pfeifer.com>
> Just omit the slashes at the ends of the two URLs please. (If you
> paste them into Firefox, say, you'll notice they end up getting stripped.
> I don't have the RFC handy right now, but for domain names without
> directories the / hasn't been necessary for fifteen or so years.)
Done.
Does the website get rebuilt automatically, or does it need to be triggered?
FX
next prev parent reply other threads:[~2017-05-27 8:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C45B76FD-56E3-4B56-AE9B-690EA082FAF0@gmail.com>
[not found] ` <alpine.LSU.2.21.1705022318590.2928@anthias.pfeifer.com>
2017-05-23 8:49 ` FX
2017-05-25 15:19 ` Mike Stump
2017-05-25 20:25 ` Gerald Pfeifer
2017-05-27 9:33 ` FX [this message]
2017-05-27 10:52 ` Gerald Pfeifer
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=5121AC76-CA60-475A-B5D2-DEA224E9212A@gmail.com \
--to=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=mikestump@comcast.net \
/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).