From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: hasufell@gentoo.org
Subject: Re: [gentoo-dev] force verbose build log as per PMS policy?
Date: Wed, 1 Aug 2012 18:07:21 +0200 [thread overview]
Message-ID: <20120801180721.29f1bd53@pomiocik.lan> (raw)
In-Reply-To: <50190F67.9060900@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
On Wed, 01 Aug 2012 13:13:43 +0200
hasufell <hasufell@gentoo.org> wrote:
> We already had a discussion about cmake-utils.eclass and forcing
> verbose build log for that which was approved:
> http://archives.gentoo.org/gentoo-dev/msg_ce7d33748936663e84a5463fbf7f4d39.xml
>
> Also we have bug https://bugs.gentoo.org/show_bug.cgi?id=384193 and
> https://bugs.gentoo.org/show_bug.cgi?id=379497
>
> I opened a tracker https://bugs.gentoo.org/show_bug.cgi?id=429308
>
> Some devs seem unsure about that or want to have a council vote on
> that https://bugs.gentoo.org/show_bug.cgi?id=429332
PMS doesn't have such a thing as a 'policy'. Gentoo can have one,
and I believe that should be discussed per Gentoo policy.
--
Best regards,
Michał Górny
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]
next prev parent reply other threads:[~2012-08-01 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 11:13 [gentoo-dev] force verbose build log as per PMS policy? hasufell
2012-08-01 15:27 ` Rich Freeman
2012-08-01 16:07 ` Michał Górny [this message]
2012-08-03 23:18 ` hasufell
2012-08-03 23:35 ` Diego Elio Pettenò
2012-08-04 19:03 ` Doug Goldstein
2012-08-04 19:18 ` hasufell
2012-08-01 16:43 ` Francesco Riosa
[not found] ` <f56376345d2d4219986fe436c23f7279@HUBCAS1.cs.stonybrook.edu>
2012-08-01 22:22 ` Richard Yao
2012-08-06 10:24 ` Chí-Thanh Christopher Nguyễn
2012-08-06 11:08 ` Michał Górny
2012-08-06 11:21 ` Michał Górny
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=20120801180721.29f1bd53@pomiocik.lan \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hasufell@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