From: Joel Brobecker <brobecker@adacore.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org,
newlib@sourceware.org, valgrind-developers@lists.sourceforge.net
Subject: FYI - git-hooks updates to be deployed
Date: Fri, 10 Nov 2017 09:52:00 -0000 [thread overview]
Message-ID: <20171109175336.jc5bvd6ils5pqg4n@adacore.com> (raw)
Hello,
Just a quick heads up to let everyone know that I'm about to update
the git-hooks on sourceware. I think the more interesting change is:
- disable all checks (revision log, style) for commits created
with "git revert". This uses a bit of a heuristic to identify
those, but the idea is to avoid having additional roadblocks
when trying to quickly revert a change which is known to be
sufficiently problematic to need the revert.
https://sourceware.org/gdb/wiki/GitHooksUsersGuide#A.22Revert.22_commits
Other changes, probably mostly irrelevant for the most part:
- Add support for hooks.no-style-checks config option
(I believe we don't do automated style-checking, at least not
in binutils-gdb.git, so probably not relevant)
- [AdaCore-specific] For repositories where a ticket number
is required (hooks.tn-required set to True), the word "minor"
in the revision log no longer waves that requirement. Instead,
users are expected to use "no-tn-check", which is less likely
to be used accidentally, and is also more explicit.
- [Gerrit] Create an error when creating a branch where there is
a .gitreview file pointing to a branch with a different name.
This is mostly to remind users that when they create a new branch
and push it, they should remember to update the defaultbranch in
their .gitreview as well. Otherwise, things can become extremely
confusing to users very quickly.
- Some minor cleanups with no associated behavior change.
--
Joel
reply other threads:[~2017-11-09 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171109175336.jc5bvd6ils5pqg4n@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).