From: Doug Goldstein <cardoe@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: patches.gentoo.org
Date: Wed, 13 Oct 2004 09:28:08 -0400 [thread overview]
Message-ID: <416D2D68.2010208@gentoo.org> (raw)
In-Reply-To: <20041013125319.GH26288@mail.lieber.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kurt Lieber wrote:
| On Tue, Oct 12, 2004 at 08:12:58PM +0100 or thereabouts, Ciaran
McCreesh wrote:
|
|>On Tue, 12 Oct 2004 15:09:45 -0400 Chris Gianelloni
|><wolf31o2@gentoo.org> wrote:
|>| 2. developer puts SRC_URI="patches.gentoo.org/${P}-$patchname" in the
|>| ebuild, at the end of the SRC_URI definition
|>
|>mirror://patches/ please.
|
|
| If by this you mean that patches should then exist in thirdpartymirrors
| with a list of servers appended to it, that's not going to fly.
|
| We adjust rsync mirrors all the time and we need the flexibility to pull a
| mirror from the rotation without any notice whatsoever. With our low TTLs
| (20min) on rsync.g.o, we can do this now. If we have to worry about what
| servers are listed in thirdpartymirrors, it's not going to work.
|
| So, SRC_URI="patches.gentoo.org/ please. Leave the round robin/load
| balancing to us.
|
| --kurt
Or you could just leave it as mirror://patches/ for ease and just
specify patches.gentoo.org in thirdpartymirrors and you'd get your load
balancing.
- --
Doug Goldstein
http://dev.gentoo.org/~cardoe
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x179106D0
Key fingerprint = 7001 5FBF BACE 9E66 3A1C 55E0 161C FF5C 1791 06D0
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBbS1nFhz/XBeRBtARAlncAJ0Rpz90jGFQlzztarVSMtC63g+ZzgCdFX5V
1LtXsmDMANm0YPSZzQewnLc=
=R4nm
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-10-13 13:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 19:09 [gentoo-dev] Proposal: patches.gentoo.org Chris Gianelloni
2004-10-12 19:12 ` Ciaran McCreesh
2004-10-12 19:32 ` George Shapovalov
2004-10-12 19:33 ` Ciaran McCreesh
2004-10-13 12:53 ` Kurt Lieber
2004-10-13 13:28 ` Doug Goldstein [this message]
2004-10-12 19:27 ` Marius Mauch
2004-10-12 19:52 ` Beber
2004-10-12 20:11 ` Marius Mauch
2004-10-12 20:10 ` Nicholas Jones
2004-10-12 20:50 ` Jeffrey Forman
2004-10-12 20:57 ` Jeffrey Forman
2004-10-12 23:20 ` Chris Gianelloni
2004-10-13 12:43 ` Kurt Lieber
2004-10-13 9:46 ` Paul de Vrieze
2004-10-13 12:19 ` Lance Albertson
2004-10-13 12:39 ` Kurt Lieber
2004-10-12 19:57 ` Nick Dimiduk
2004-10-12 19:57 ` Ciaran McCreesh
2004-10-12 20:17 ` Chris Gianelloni
2004-10-12 22:04 ` Mike Frysinger
2004-10-13 13:05 ` Kurt Lieber
2004-10-13 15:16 ` Ciaran McCreesh
2004-10-14 12:07 ` Kurt Lieber
2004-10-15 15:13 ` Xavier Neys
2004-10-14 20:38 ` Dylan Carlson
2004-10-14 21:05 ` Mark Loeser
2004-10-15 1:00 ` Chris Gianelloni
2004-10-14 22:08 ` [gentoo-dev] Patch filename conventions (WAS: Proposal: patches.gentoo.org) Dylan Carlson
2004-10-14 22:14 ` Mike Frysinger
2004-10-15 2:20 ` Dylan Carlson
2004-10-15 2:58 ` Donnie Berkholz
2004-10-15 4:24 ` Dylan Carlson
2004-10-15 5:13 ` Donnie Berkholz
2004-10-15 6:01 ` Dylan Carlson
2004-10-15 6:04 ` Robin H. Johnson
2004-10-15 12:16 ` Kurt Lieber
2004-10-15 0:49 ` [gentoo-dev] Proposal: patches.gentoo.org Chris Gianelloni
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=416D2D68.2010208@gentoo.org \
--to=cardoe@gentoo.org \
--cc=gentoo-dev@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