public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: note about the git-hooks install for binutils-gdb.git
Date: Sun, 23 Feb 2020 04:23:00 -0000	[thread overview]
Message-ID: <20200223042338.GD5910@adacore.com> (raw)

Hi everyone,

We had a breakage with the hooks this weekend, which was caused
by some changes by someone coming in with the usual team attitude
that often serves us so well. Unfortunately, that change caused
emailing to break.

I would like to request that we don't make changes to the hooks
without coordinating them either through either GitHub,
or else through me if that's simpler for you guys. Knowing the hooks
well, I can help you design the change, and I might even make
that change for you! But most of all, I will get it tested through
the extensive testsuite I wrote.  It may not seem like it, but
I developped the hooks treating it as if it was critical software,
so as to ensure maximum availability.

If, during the weekend, you tried to push some changes to
the binutils-gdb.git repository, and got the following error:

        | $ git push upstream master:hello
        | ...
 !! ->  | remote: Traceback (most recent call last):
 !! ->  | remote:   File "hooks/post_receive.py", line 126, in <module>
 !! ->  | remote:     post_receive(refs_data, args.submitter_email)
 !! ->  | remote: NameError: name 'args' is not defined
        | To ssh://sourceware.org/git/binutils-gdb.git
        |  * [new branch]                master -> hello

Then were you were hit by it, and emails for that update have not
been sent. You can contact me in private, and I will get them
resent.

Thank you,
-- 
Joel

             reply	other threads:[~2020-02-23  4:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23  4:23 Joel Brobecker [this message]
2020-02-25 23:53 ` Christian Biesinger via binutils
2020-02-26  2:34   ` 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=20200223042338.GD5910@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@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).