From: Corinna Vinschen <vinschen@redhat.com>
To: Joel Brobecker via Overseers <overseers@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
Ivo Raisr <ivosh@ivosh.net>,
Carlos O'Donell <carlos@systemhalted.org>,
Joseph Myers <joseph@codesourcery.com>,
Jeff Johnston <jjohnstn@redhat.com>
Subject: Re: transition git-hooks on sourceware.org to Python 3.x
Date: Thu, 20 Jan 2022 11:04:47 +0100 [thread overview]
Message-ID: <Yekzv6ue213z+nmL@calimero.vinschen.de> (raw)
In-Reply-To: <Yejyu+tGIFfbeTcP@adacore.com>
On Jan 20 09:27, Joel Brobecker via Overseers wrote:
> > > For binutils-gdb, the transition has been made a few weeks ago,
> > > and so far so good :). So I'm inviting you all to transition
> > > this new version at your convenience.
> > >
> > > Remember that, if your project's configuration calls some Python
> > > hooks, you'll probably want to double-check that they are compatible
> > > with Python 3.x!
> >
> > I did the same for newlib-cygwin.git just a couple of minutes ago.
> > Hopefully this works as nicely as for biunutils-gdb :}
>
> No news must be good news. Well done, Corinna :).
Actually, looks good so far. We only had a single, local python2
script which I 2to3-d and appears to work as well.. Thanks for a
smooth transition!
Corinna
next prev parent reply other threads:[~2022-01-20 10:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 11:32 Joel Brobecker
2021-12-13 9:23 ` Mark Wielaard
2021-12-15 9:30 ` Ivo Raisr
2021-12-16 2:16 ` Joel Brobecker
2021-12-13 11:35 ` Corinna Vinschen
2021-12-13 11:47 ` Joel Brobecker
2021-12-13 22:20 ` Joseph Myers
2021-12-14 3:39 ` Joel Brobecker
2021-12-17 2:46 ` Joel Brobecker
2021-12-19 4:45 ` Joel Brobecker
2021-12-20 5:10 ` Joel Brobecker
2022-01-16 10:06 ` Joel Brobecker
2022-01-17 10:02 ` Corinna Vinschen
2022-01-20 5:27 ` Joel Brobecker
2022-01-20 10:04 ` Corinna Vinschen [this message]
2022-01-20 13:54 ` Joel Brobecker
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=Yekzv6ue213z+nmL@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=brobecker@adacore.com \
--cc=carlos@systemhalted.org \
--cc=ivosh@ivosh.net \
--cc=jjohnstn@redhat.com \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).