From: Lance Albertson <ramereth@gentoo.org>
To: Paul de Vrieze <pauldv@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: patches.gentoo.org
Date: Wed, 13 Oct 2004 07:19:48 -0500 [thread overview]
Message-ID: <1097669988.10155.6.camel@mirage> (raw)
In-Reply-To: <200410131146.55484.pauldv@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Wed, 2004-10-13 at 04:46, Paul de Vrieze wrote:
> On Tuesday 12 October 2004 21:27, Marius Mauch wrote:
> > On 10/12/04 Chris Gianelloni wrote:
> > > The developer would use this temporary location as follows:
> > >
> > > 1. developer creates an ebuild which needs a patch
> > > 2. developer puts SRC_URI="patches.gentoo.org/${P}-$patchname" in the
> > > ebuild, at the end of the SRC_URI definition
> >
> > make that
> > SRC_URI="mirror://gentoo/patchname http://patches.gentoo.org/patchname"
> > ($GENTOO_MIRRORS can be empty)
>
> What is the difference from just putting these files in your own dev
> space? If they just exist on dev.gentoo.org the developers themselves can
> arange removing etc.
The difference is, dev is a single point of failure, plus you're
suggesting that dev become a single mirror for that file. It could
potentially create an issue of ddos. The suggestion we're making is
coming up with a solution that is as simple as putting on your dev
space, but its distributed on several servers we already have.
--
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure
---
GPG Public Key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
ramereth/irc.freenode.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-13 12:19 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
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 [this message]
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=1097669988.10155.6.camel@mirage \
--to=ramereth@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pauldv@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