Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: FYI: git-hooks update on sourceware.org
Date: Fri, 7 Aug 2020 08:44:23 -0700	[thread overview]
Message-ID: <20200807154423.GB3362@adacore.com> (raw)

Hey Team,

Just to let you know, I've just done an update of the git-hooks
installed on sourceware.org and used by our binutils-gdb repository.

I've also undone a change that was made locally by Frank ages ago
which I am hoping is no longer necessary:

    -exec git-update-server-info
    +exec git update-server-info

This update brings a series of improvements made mostly in order to
answer GCC's specific needs. If you're curious about the list of
changes, you can have a look at the list of changes made since
commit 087a8bcdf0de43bc196ccdf83c2f572fef604f75 at
https://github.com/adacore/git-hooks.

One of the enhancements this update does bring is the ability to
provide custom commit validation, something I believe Simon asked
about, to prevent us from pushing commits we "git am"-ed using
an Author set to "xxx via Gdb-patches <gdb-patches@...>". Take
a look at the hooks.commit-extra-checker option in the doc. If
someone writes the script, I can get it installed.

These changes have been extensively tested, and we've been using
the same version at AdaCore for over a week, now; but do let me
know if you have any issues.

-- 
Joel


             reply	other threads:[~2020-08-07 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07 15:44 Joel Brobecker [this message]
2020-08-07 15:50 ` Joel Brobecker
2020-08-07 16:00   ` Simon Marchi
2020-08-07 16:02     ` Simon Marchi
2020-08-07 16:21       ` Joel Brobecker
2020-08-07 16:27         ` H.J. Lu
2020-08-07 16:44           ` Joel Brobecker
2020-08-10 16:57         ` 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=20200807154423.GB3362@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