public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org,
	Wynn Wolf Arbor <wolf@oriole.systems>
Subject: Re: [gentoo-portage-dev] [PATCH 0/2] Use consistent list of booleans & validate verify-commit-signature
Date: Thu, 2 Jul 2020 15:17:31 -0700	[thread overview]
Message-ID: <e88f9477-bfcd-31f5-25b3-798bdc56d094@gentoo.org> (raw)
In-Reply-To: <20200702155018.82993-1-wolf@oriole.systems>


[-- Attachment #1.1: Type: text/plain, Size: 1432 bytes --]

On 7/2/20 8:50 AM, Wynn Wolf Arbor wrote:
> Hi,
> 
> Whilst configuring a bunch of overlay repositories via repos.conf, I
> discovered that not all boolean options take the same values. Some only
> take 'true' and 'false', others are documented only as 'yes' or 'no',
> but take 'true', 'false', 'yes', and 'no'. This is inconsistent and can
> lead to very confusing outcomes, so I decided to write a patch.
> 
> I came across https://bugs.gentoo.org/703698 whilst working on this, and
> since my work was tangentially related, decided to fix that as well.
> 
> Wynn Wolf Arbor (2):
>       repos.conf: Use consistent list of values for boolean options
>       git: Verify boolean values passed to sync-git-verify-commit-signature
> 
>  lib/portage/repository/config.py         |  4 +--
>  lib/portage/sync/modules/git/__init__.py | 11 ++++++++
>  lib/portage/sync/modules/git/git.py      |  2 +-
>  lib/portage/sync/modules/rsync/rsync.py  |  2 +-
>  man/portage.5                            | 45 +++++++++++++++-----------------
>  5 files changed, 36 insertions(+), 28 deletions(-)


Thanks! I've merged both patches, with a couple of additional lower()
calls for case insensitivity:

https://gitweb.gentoo.org/proj/portage.git/commit/?id=141ef203661248a2c29945f8c6770ce0c242eaf0
https://gitweb.gentoo.org/proj/portage.git/commit/?id=33b08baff4825bf84f639cf213de92ed36f76771
-- 
Thanks,
Zac




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

      parent reply	other threads:[~2020-07-02 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 15:50 [gentoo-portage-dev] [PATCH 0/2] Use consistent list of booleans & validate verify-commit-signature Wynn Wolf Arbor
2020-07-02 15:50 ` [gentoo-portage-dev] [PATCH 1/2] repos.conf: Use consistent list of values for boolean options Wynn Wolf Arbor
2020-07-02 15:50 ` [gentoo-portage-dev] [PATCH 2/2] git: Verify boolean values passed to sync-git-verify-commit-signature Wynn Wolf Arbor
2020-07-02 22:17 ` Zac Medico [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=e88f9477-bfcd-31f5-25b3-798bdc56d094@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    --cc=wolf@oriole.systems \
    /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