This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC Git hooks
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: Jason Merrill <jason at redhat dot com>, Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>, gcc Mailing List <gcc at gcc dot gnu dot org>, Gerald Pfeifer <gerald at pfeifer dot com>, Daniel Berlin <dberlin at dberlin dot org>
- Date: Fri, 10 Jan 2020 15:52:58 +0000
- Subject: Re: GCC Git hooks
- Ironport-sdr: h8/RegNQ1PYXuRKxgCG4nzmCrduiFrdCM4PRNFS5UwDLp+96lmmjfuXvstO72/LEizCcmw9usY BcMD9kqLbeblKcpsxXOf9143bsyECUriGnt9Xd1Gdbfk8jHLtw9QRIP/5LxWqLkk0Y54p0Q6ph opAeIGIo5vOBP3OcLyuG8OgZHrYxg9dlfgYxI35s8MfdyrfeO56NAKQ8XLRlUQB4mFa3Ml86nA qZl1IUdUmRTMV6ykiYHvV+WIBSr+GWBiYFz4LbAr6KYCs7/9vdgx/VsMi5noAUE3SAaOwFgsBG j4g=
- Ironport-sdr: VKxheseA5v7KQ4iM2/onzTFLKVZtyRqszg4HoN4LBb4iYE5ApOz8cfAHSmqRm8aTsrzhfa9rb8 OYYvsmafnpoifxQdq758kWoHqQtounXgOkMStm60/toSFY/hhDyMTqicIuexZAx6qq2oaszC1g Z0ZykPZTYQFRhjjpvnS+NIJtaCpKsaMsjX/DhnfFPk0UWwi8p1McP3fG3LEfogtFrRQVv19jqy ZWRZEelqKkE8G3dieWc3XAiqCIuz9JA71HsrnhoUla6cw+tNbW9DjkLjKRL4hcLqlr3C8jbpKR S8U=
- References: <CADzB+2mqKfG2iEfHZXsv5qJ_U8NQ-cGTgvGRgPWi-5mj3Hot_A@mail.gmail.com> <20190916150650.GB4945@adacore.com> <alpine.DEB.2.21.2001091417030.4040@digraph.polyomino.org.uk> <alpine.DEB.2.21.2001092158480.27516@digraph.polyomino.org.uk>
On Thu, 9 Jan 2020, Joseph Myers wrote:
> Concretely, these are the changes I'm currently using to configure the
> hooks in a way I think appropriate for GCC, and it would be useful if the
> hooks could support such configuration in a more generic way in future so
> that we can stop using a GCC-specific patched installation of the hooks.
> The following features are hardcoded that didn't seem to have a way to
> configure them:
Plus one further change now: if a newly created branch is in refs/heads/,
require it to be in refs/heads/devel/ or refs/heads/releases/ (i.e.
enforce a particular branch naming convention, in particular to prevent
mistakes where people accidentally push a branch into refs/heads/ because
their push configuration for user or vendor branches was wrong).
--
Joseph S. Myers
joseph@codesourcery.com