From: Joe Perches <joe@perches.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Scott Branden <scott.branden@broadcom.com>
Cc: Finn Behrens <me@kloenk.de>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] diffconfig: use python3 instead of python in Shebang line
Date: Thu, 21 Jan 2021 18:18:45 -0800 [thread overview]
Message-ID: <b9c303e70dc4f8573bebb6bb07c98daa25ea0fba.camel@perches.com> (raw)
In-Reply-To: <CAK7LNAQEvej1_UrS6s1+vwdei8cK1UW8b5erYc-6Ggu25oC0cg@mail.gmail.com>
On Fri, 2021-01-22 at 05:25 +0900, Masahiro Yamada wrote:
> On Fri, Jan 22, 2021 at 2:17 AM Scott Branden
> <scott.branden@broadcom.com> wrote:
> >
> > Use python3 instead of python in diffconfig Shebang line.
> > python2 was sunset January 1, 2000 and environments do not need
> > to support python any more.
python2 was sunset Jan 1, 2020, not 20 years before that.
https://www.python.org/doc/sunset-python-2/
next prev parent reply other threads:[~2021-01-22 2:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 17:07 [PATCH] diffconfig: use python3 instead of python in Shebang line Scott Branden
2021-01-21 20:25 ` Masahiro Yamada
2021-01-21 20:31 ` Andy Shevchenko
2021-01-21 20:35 ` Andy Shevchenko
2021-01-21 20:56 ` Scott Branden
2021-01-21 22:06 ` Masahiro Yamada
2021-01-22 9:34 ` Andy Shevchenko
2021-01-22 15:50 ` Joe Perches
2021-01-22 17:16 ` Masahiro Yamada
2021-01-22 17:52 ` Joe Perches
2021-01-21 20:44 ` Scott Branden
2021-01-22 2:18 ` Joe Perches [this message]
2021-01-22 16:46 ` Scott Branden
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=b9c303e70dc4f8573bebb6bb07c98daa25ea0fba.camel@perches.com \
--to=joe@perches.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=me@kloenk.de \
--cc=pombredanne@nexb.com \
--cc=scott.branden@broadcom.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.