public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PR mass closing
Date: Sat, 16 May 2020 22:16:31 +0200	[thread overview]
Message-ID: <acfee50c65019a741639cc618edff8eb1cb9a851.camel@gentoo.org> (raw)
In-Reply-To: <5ec02c31.1c69fb81.ed7e.2897@mx.google.com>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

First of all, please don't send HTML mail.

On Sat, 2020-05-16 at 20:08 +0200, lssndrbarbieri@gmail.com wrote:
> Was it necessary to mass close my PR on GitHub? I’ve lost quite some time to make them and I’m a bit upset.

I'm sorry but if you start mass-filing pull requests without consulting
anyone first, you have only yourself to blame.  I am also upset that
I had to manually close a dozen PRs.

> How much we have to wait to get rid of python2?

The rule of thumb would be until we get rid of all packages requiring
Python 2.

> The earlier the better because portage want to pull in python2 stuff if available even when I don’t want.

Then set PYTHON_TARGETS appropriately.  Duplicating ebuild revisions
doesn't help anyone.  As explained on the pull request.  Neither does
complaining.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  parent reply	other threads:[~2020-05-16 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 18:08 [gentoo-dev] PR mass closing lssndrbarbieri
2020-05-16 19:30 ` Mike Gilbert
2020-05-16 20:16 ` Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-16 18:08 lssndrbarbieri

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=acfee50c65019a741639cc618edff8eb1cb9a851.camel@gentoo.org \
    --to=mgorny@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