From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Questions about CVS locations and GID...
Date: Thu, 6 Oct 2005 00:03:18 +0100 [thread overview]
Message-ID: <20051006000318.77ed8757@snowdrop.home> (raw)
In-Reply-To: <20051005225336.GJ10159@nightcrawler>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Wed, 5 Oct 2005 17:53:36 -0500 Brian Harring <ferringb@gentoo.org>
wrote:
| On Wed, Oct 05, 2005 at 11:29:56PM +0100, Ciaran McCreesh wrote:
| > On Wed, 5 Oct 2005 16:16:06 -0500 Kito <kito@gentoo.org> wrote:
| > | > b) assume that you'll not have to modify ebuilds
| > |
| > | I don't think anyone(devs) has made this naive assumption have
| > | they?
| >
| > pvdabeel has for pathspec.
| >
| > | > and c)
| > | > demand that as soon as it's available, it works for all ebuilds.
| > |
| > | I don't think anyone(devs) has made this naive demand have they?
| >
| > pvdabeel has for pathspec.
|
| You're not talking to pvdabeel right now, so kindly be quiet about
| him.
Oh come off it. You claim that no dev has made this naive demand when
at least one quite clearly has on several occasions. All three of my
points are entirely relevant to the discussion, since every other time
this has come up at least one said mistakes has been made.
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
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-10-05 23:03 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 18:35 [gentoo-portage-dev] Questions about CVS locations and GID m h
2005-10-05 19:54 ` Ciaran McCreesh
2005-10-05 20:06 ` Alec Joseph Warner
2005-10-05 20:18 ` m h
2005-10-05 20:25 ` Alec Joseph Warner
2005-10-05 20:24 ` Brian Harring
2005-10-05 20:48 ` m h
2005-10-05 21:10 ` Brian Harring
2005-10-05 21:52 ` m h
2005-10-05 22:02 ` Brian Harring
2005-10-05 23:01 ` m h
2005-10-05 23:10 ` Brian Harring
2005-10-05 20:57 ` Ciaran McCreesh
2005-10-05 21:13 ` Brian Harring
2005-10-05 22:31 ` Ciaran McCreesh
2005-10-05 23:00 ` Brian Harring
2005-10-05 23:14 ` Ciaran McCreesh
2005-10-05 23:22 ` Brian Harring
2005-10-05 23:38 ` Ciaran McCreesh
2005-10-05 23:40 ` Brian Harring
2005-10-06 0:13 ` Ciaran McCreesh
2005-10-06 1:01 ` Brian Harring
2005-10-06 1:07 ` Ciaran McCreesh
2005-10-06 1:17 ` Brian Harring
2005-10-06 1:23 ` Ciaran McCreesh
2005-10-06 1:32 ` Brian Harring
2005-10-06 1:40 ` Ciaran McCreesh
2005-10-06 1:48 ` Brian Harring
2005-10-06 2:01 ` Ciaran McCreesh
2005-10-06 2:39 ` Brian Harring
2005-10-06 11:51 ` Ciaran McCreesh
2005-10-06 12:08 ` Jason Stubbs
2005-10-06 13:07 ` Alec Warner
2005-10-06 18:29 ` Ciaran McCreesh
2005-10-06 18:42 ` Brian Harring
2005-10-06 19:11 ` Ciaran McCreesh
2005-10-06 1:56 ` Kito
2005-10-06 2:02 ` Ciaran McCreesh
2005-10-06 2:11 ` Kito
2005-10-05 23:27 ` Alec Warner
2005-10-05 23:38 ` m h
2005-10-05 23:46 ` Alec Warner
2005-10-05 21:16 ` Kito
2005-10-05 21:34 ` Brian Harring
2005-10-05 22:29 ` Ciaran McCreesh
2005-10-05 22:53 ` Brian Harring
2005-10-05 23:03 ` Ciaran McCreesh [this message]
2005-10-05 23:21 ` Brian Harring
2005-10-06 4:14 ` Finn Thain
2005-10-06 4:22 ` Brian Harring
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=20051006000318.77ed8757@snowdrop.home \
--to=ciaranm@gentoo.org \
--cc=gentoo-portage-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