From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] RFC: moving API-related DTDs into api.gentoo.org
Date: Tue, 2 Jun 2015 11:38:50 -0400 [thread overview]
Message-ID: <20150602153850.GF23039@vapier> (raw)
In-Reply-To: <55115E06.3040705@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On 24 Mar 2015 13:52, Alex Legler wrote:
> Taking into account that not everything belonging to these DTDs is on
> api.g.o, we would be even hurting permanence of the URLs by moving them,
> and the overall lack of a clear gain, I'd keep them on gentoo.org in one
> central DTD location, i.e. the current gentoo.org/dtd/.
why can't g.o/dtd/ be a simple redirect to api.g.o/dtd/ ? it makes sense in my
mind for all the dtd files to live in api.g.o.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-06-02 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 9:37 [gentoo-project] RFC: moving API-related DTDs into api.gentoo.org Michał Górny
2015-03-24 11:14 ` Ben de Groot
2015-03-24 12:52 ` Alex Legler
2015-06-02 15:38 ` Mike Frysinger [this message]
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=20150602153850.GF23039@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-project@lists.gentoo.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