From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: Mike Gilbert <floppym@gentoo.org>
Subject: Re: [gentoo-portage-dev] [PATCH] repoman: remove check for addpredict
Date: Thu, 05 Mar 2020 21:59:51 +0100 [thread overview]
Message-ID: <a80f37a6d03f948247efe319e7548b0eb0f782a8.camel@gentoo.org> (raw)
In-Reply-To: <20200305203016.2887588-1-floppym@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Thu, 2020-03-05 at 15:30 -0500, Mike Gilbert wrote:
> This function has not been deprecated, and developers generally have a
> good reason for using it. A repoman warning for this is just noise.
>
> No reason was given when this check was added in 2010, and it was requested
> by a developer who has since retired.
>
If you want to remove this class of warnings, I'd suggest removing
the one for -j1 as well. Same argument.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2020-03-05 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 20:30 [gentoo-portage-dev] [PATCH] repoman: remove check for addpredict Mike Gilbert
2020-03-05 20:59 ` Michał Górny [this message]
2020-03-05 21:04 ` Mike Gilbert
2020-03-05 21:24 ` Zac Medico
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=a80f37a6d03f948247efe319e7548b0eb0f782a8.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=floppym@gentoo.org \
--cc=gentoo-portage-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