From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] app-arch ambiguous?
Date: Tue, 22 Mar 2005 21:52:10 +0000 [thread overview]
Message-ID: <20050322215210.2b0a38da@snowdrop> (raw)
In-Reply-To: <46059ce105032213446bc78e2e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
On Tue, 22 Mar 2005 16:44:34 -0500 Dan Meltzer
<parallelgrapefruit@gmail.com> wrote:
| It would save bandwith though!
No it wouldn't, because we'd end up with a stupidly large set of
updates/ files.
--
Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-22 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 21:16 [gentoo-dev] app-arch ambiguous? Dan Meltzer
2005-03-22 21:21 ` Ciaran McCreesh
2005-03-22 21:25 ` Dan Meltzer
2005-03-22 21:37 ` Ciaran McCreesh
2005-03-22 21:44 ` Dan Meltzer
2005-03-22 21:52 ` Ciaran McCreesh [this message]
2005-03-22 21:47 ` Chris Gianelloni
2005-03-23 1:07 ` Anthony Gorecki
2005-03-23 1:17 ` Ciaran McCreesh
2005-03-23 1:28 ` Anthony Gorecki
2005-03-23 1:42 ` Ciaran McCreesh
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=20050322215210.2b0a38da@snowdrop \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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