From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Message from emerge re transfig is ineffective
Date: Mon, 14 Aug 2006 08:57:47 +0100 [thread overview]
Message-ID: <20060814085747.165a462d@hactar.digimed.co.uk> (raw)
In-Reply-To: <9acccfe50608131935w731587c0m9c0971406aa19161@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
On Sun, 13 Aug 2006 19:35:59 -0700, Kevin O'Gorman wrote:
> > It's a QA message from portage to the developer of the ebuild, ignore
> > it.
> Isn't there some way "they" could flag such messages so it doesn't
> look like a peremptory command I have to jump up and perform?
Removing strict from FEATURES should stop you seeing these AFAIR.
--
Neil Bothwick
He who laughs last probably made a back-up.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-14 8:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:37 [gentoo-user] Message from emerge re transfig is ineffective Kevin O'Gorman
2006-08-09 16:25 ` Neil Bothwick
2006-08-14 2:35 ` Kevin O'Gorman
2006-08-14 7:57 ` Neil Bothwick [this message]
2006-08-15 5:51 ` Kevin O'Gorman
2006-08-15 8:10 ` Neil Bothwick
2006-08-15 14:34 ` Kevin O'Gorman
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=20060814085747.165a462d@hactar.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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