From: Joel Brobecker <brobecker@adacore.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org,
newlib@sourceware.org, valgrind-developers@lists.sourceforge.net
Subject: Re: FYI - git-hooks recents update to be deployed in a couple of weeks
Date: Mon, 24 Jul 2017 18:54:00 -0000 [thread overview]
Message-ID: <20170724181552.wi7bwe6fiztevlvy@adacore.com> (raw)
In-Reply-To: <20170705163620.ymctjkpkwy2v43ci@adacore.com>
> This is just a heads up that I've made a number of changes to
> the git-hooks which you currently use. The commits introduce
> the following changes:
>
> - passing the filename to the style-checker via stdin
> rather than on the command line; this is an enabler for...
>
> - calling the style-checker only once per commit.
>
> - Fix a crash when the value of a config option (any config option)
> in the project.config file (in the refs/meta/config branch) spans
> multiple lines
>
> - Support for using one entry per item in the project.config file
> when the configuration is a list. This is an alternative to using
> one entry with a comma-separated value.
>
> - Support for a new configuration, called hooks.frozen-ref, which
> is a list of references for which updates are not allowed (used
> when branches are retired).
>
> The first 2 changes might have an impact on your project if you had
> a style-checker configured.
>
> For various reasons, I will hold those changes until at least July 24th.
> So if your project is impacted, you have at least 2 weeks to plan for
> the transition. Let me know if you need more time.
I just installed the udpates. Let me know if there are any issues.
--
Joel
prev parent reply other threads:[~2017-07-24 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 16:36 Joel Brobecker
2017-07-24 18:54 ` Joel Brobecker [this message]
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=20170724181552.wi7bwe6fiztevlvy@adacore.com \
--to=brobecker@adacore.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=newlib@sourceware.org \
--cc=valgrind-developers@lists.sourceforge.net \
/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).