From: Hans de Graaff <graaff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/3] ruby-ng.eclass: improve error when no valid Ruby in USE_RUBY
Date: Fri, 31 Mar 2023 11:28:57 +0200 [thread overview]
Message-ID: <88e081d7188b2764e69a1c471410b20ea106c45c.camel@gentoo.org> (raw)
In-Reply-To: <20230329153934.4053851-1-sam@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
On Wed, 2023-03-29 at 16:39 +0100, Sam James wrote:
> This means we don't get confusing *DEPEND/REQUIRED_USE errors about
> it being
> unparseable and instead just get a straightforward die message
> indicating
> the problem.
All three patches look good to me.
Hans
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-31 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 15:39 [gentoo-dev] [PATCH 1/3] ruby-ng.eclass: improve error when no valid Ruby in USE_RUBY Sam James
2023-03-29 15:39 ` [gentoo-dev] [PATCH 2/3] ruby-ng.eclass: don't quote IUSE in has test Sam James
2023-03-29 15:39 ` [gentoo-dev] [PATCH 3/3] ruby-fakegem.eclass: don't double-add USE=doc/test Sam James
2023-03-29 15:49 ` Petr Vaněk
2023-03-31 9:28 ` Hans de Graaff [this message]
2023-03-31 20:27 ` [gentoo-dev] [PATCH 1/3] ruby-ng.eclass: improve error when no valid Ruby in USE_RUBY Sam James
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=88e081d7188b2764e69a1c471410b20ea106c45c.camel@gentoo.org \
--to=graaff@gentoo.org \
--cc=gentoo-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