From: Joel Brobecker <brobecker@adacore.com>
To: overseers@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
Joseph Myers <joseph@codesourcery.com>,
Carlos O'Donell <carlos@systemhalted.org>,
Corinna Vinschen <vinschen@redhat.com>,
Ivo Raisr <ivosh@ivosh.net>
Subject: Re: transition git-hooks on sourceware.org to Python 3.x
Date: Mon, 20 Dec 2021 09:10:31 +0400 [thread overview]
Message-ID: <YcAQRwzBoipzDXp4@adacore.com> (raw)
In-Reply-To: <Yb648+Etld0X1+sm@adacore.com>
> My plan is to transition the binutils-gdb repository to it on Monday
> morning (European timezone). To do so, what I will do is:
>
> $ /git/binutils-gdb.git
> $ mv hooks{,.legacy-python2} \
> && ln -s /home/gdbadmin/shared-scripts/git-hooks-wrapper/hooks hooks
This is now done.
I tested with a first simple patch push, and realized I had forgotten
to update ...
/git/binutils-gdb.git/hooks-bin
... first (missing Python3-ization of email_to.py). So I got an error
during the emailing, while the push went through.
I therefore did...
| % cd /git/binutils-gdb.git/hooks-bin/
| % git pull --rebase
| remote: Enumerating objects: 5, done.
| remote: Counting objects: 100% (5/5), done.
| remote: Compressing objects: 100% (3/3), done.
| remote: Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
| Unpacking objects: 100% (3/3), 329 bytes | 41.00 KiB/s, done.
| From /home/gdbadmin/GDBADMIN-BARE-REPOS/hooks-bin
| 0018300..0d31c4b master -> origin/master
| Updating 0018300..0d31c4b
| Fast-forward
| email_to.py | 4 ++--
| 1 file changed, 2 insertions(+), 2 deletions(-)
| Current branch master is up to date.
... found another trivial change I could make, and pushed it,
this time with no error.
I double-checked the email for my commit has been sent to gdb-cvs:
https://sourceware.org/pipermail/gdb-cvs/2021-December/052054.html
I'll warn the users on gdb-patches to let me know if they see any issue.
--
Joel
next prev parent reply other threads:[~2021-12-20 5:10 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 [this message]
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
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=YcAQRwzBoipzDXp4@adacore.com \
--to=brobecker@adacore.com \
--cc=carlos@systemhalted.org \
--cc=ivosh@ivosh.net \
--cc=joseph@codesourcery.com \
--cc=overseers@sourceware.org \
--cc=vinschen@redhat.com \
/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).