From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Re: [PATCH] Allocate __* for package manager internals, blacklist it for ebuilds.
Date: Sun, 16 Sep 2012 16:06:19 +0100 [thread overview]
Message-ID: <20120916160619.1e39619f@googlemail.com> (raw)
In-Reply-To: <20120916072418.GJ28593@localhost>
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
On Sun, 16 Sep 2012 00:24:18 -0700
Brian Harring <ferringb@gmail.com> wrote:
> The annoying thing about that list is that 'prep' has a few scenarios
> where it has to be used to get things done.
The thing about the prep* functions is that no-one seems willing to lock
down their behaviour.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-16 15:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1347327593%2d1144-1-git-send-email-ferringb@gmail.com>
2012-09-16 6:45 ` [gentoo-pms] Re: [PATCH] Allocate __* for package manager internals, blacklist it for ebuilds Ulrich Mueller
2012-09-16 7:24 ` Brian Harring
2012-09-16 15:06 ` Ciaran McCreesh [this message]
2012-09-16 16:14 ` Ulrich Mueller
2012-09-18 23:59 ` Brian Harring
2012-09-19 5:22 ` Ulrich Mueller
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=20120916160619.1e39619f@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-pms@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