public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: patches.gentoo.org
Date: Tue, 12 Oct 2004 22:11:21 +0200	[thread overview]
Message-ID: <20041012221121.62956a26@andy.genone.homeip.net> (raw)
In-Reply-To: <416C35F8.9030402@setibzh.com>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

On 10/12/04  Beber wrote:

> Marius Mauch wrote:
> 
> >>dev.gentoo.org:/space/distfiles-local
> >>    
> >>
> > 3. developer uploads patch to dev.gentoo.org:/space/patches-local
> > and
> >
> >
> >I don't see a reason to separate patches from distfiles.
> >  
> >
> I think my english is bad, tell if you don't understand what I want to
> 
> say :/
> 
> I think that it's not to separate patch from distfiles (a lot are 
> already avaible) but to have a emerge sync faster and less bandwith 
> consumer.
> many many patch are on sync server, many are not apply due to proc 
> architecture or USE flag.
> Thoses patch that are on distfiles server aren't necessary download
> like on sync
> I think that it can be a way to take for futur.
> 
> Like an other thing (for bandwith use) : if an update of a pacquet is 
> avaible : why download are the new sources instead of just a patch ?

You're talking about something completely different, I'm just talking
about the location on dev.gentoo.org, that has nothing to do wether a
patch or a full tarball is used.

Marius

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-10-12 20:11 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 [this message]
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=20041012221121.62956a26@andy.genone.homeip.net \
    --to=genone@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