From: rindeal <dev.rindeal@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: kde@gentoo.org, tommy@gentoo.org
Subject: Re: [gentoo-dev] cmake-utils.eclass: fixes to ninja MAKEOPTS conversion
Date: Thu, 26 May 2016 15:24:25 +0200 [thread overview]
Message-ID: <CANgLvuCdDXCd=quF9fvr10mMeVF6eR75LZO2DeTv1xH+=hQXGA@mail.gmail.com> (raw)
In-Reply-To: <20160526101033.7af217dc.mgorny@gentoo.org>
> After the three-month review period I've decided to go ahead and push
> it.
Please notice that there is a much more comprehensive proposal for
_ninjaopts_from_makeopts() in the review queue -
https://github.com/gentoo/gentoo/pull/1481
prev parent reply other threads:[~2016-05-26 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 19:01 [gentoo-dev] cmake-utils.eclass: fixes to ninja MAKEOPTS conversion Michał Górny
2016-02-28 19:01 ` [gentoo-dev] [PATCH 1/2] cmake-utils.eclass: _ninjaopts_from_makeopts, fix handling of -k Michał Górny
2016-02-28 19:01 ` [gentoo-dev] [PATCH 2/2] cmake-utils.eclass: _ninjaopts_from_makeopts, fix plain '-j' and '-l' Michał Górny
2016-05-26 8:10 ` [gentoo-dev] cmake-utils.eclass: fixes to ninja MAKEOPTS conversion Michał Górny
2016-05-26 13:24 ` rindeal [this message]
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='CANgLvuCdDXCd=quF9fvr10mMeVF6eR75LZO2DeTv1xH+=hQXGA@mail.gmail.com' \
--to=dev.rindeal@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kde@gentoo.org \
--cc=tommy@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