This is the mail archive of the
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 18:15:30 +0000
- Subject: Re: GCC Git hooks
- Ironport-sdr: 9fPV88RP1CCND7V18M4YQIKyLp+P6qTr3tirjJKCAi+bJWDt3baIrt4+1KQUEH3ezDQW4y9QlL TLjtxICvTp2SqAeQPgtqW+zd7fUU4so2IlGVSX77LGRlQxFuwcgRn1Xm5BzyR1t6rTCTiYBKtW 2MB/yuumkPGYREvcxfgaIjmSmStlBPJwLEv+IGfMVxXemqWWefM2NHKDFkGsDiaaDtJJhYmc6m NQbW99TwP3rUlPy6NoaszANFq8oV4Cu6om15FQqrK1lHCmhOygx4lVDiNlkIckb0KasKp7aYCb A7o=
- Ironport-sdr: 2508CgCC2PXM7+YqsfvR0BFDMy3EUZ8dIJwUrT3N6rWitXkCb5mOTPDkMhCmISHQf7g+Z33NS/ FOQxM+uxrAcx0fSAXLhLy92Q+VyTst899t+8E3IIa9fm7ruk/DzhGcb9xE4A+cut93EG7sHVIR WsYDTnPBj7gxnLP0KrqijDxzBGSHm8fcwWKwt5punSVpwKu9xWAMu8twxGE/CSl8CaqKfViwSs DDCHAvZOcGMDFoKv+iYntJT+QFDJyirFRyWamXFRdZuIBkRnMmwnvwBYIJZCVRgHTYiamJc6Kn s+I=
- References: <CADzB+2mqKfG2iEfHZXsv5qJ_U8NQ-cGTgvGRgPWi-5mj3Hot_A@mail.gmail.com> <20190916150650.GB4945@adacore.com> <alpine.DEB.email@example.com> <alpine.DEB.firstname.lastname@example.org> <alpine.DEB.email@example.com> <20200110180049.GH3313@adacore.com>
On Fri, 10 Jan 2020, Joel Brobecker wrote:
> > 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).
> I'm having a hard time understanding this requirement.
> You want to say that, before branch "<xxx>" gets created, you want
> to verify that a branch named either "devel/<xxx>" or "releases/<xxx>"
> does exist?
No. What we want to ensure is that people don't accidentally create a
branch called refs/heads/foo when they should (by our naming conventions)
have created one called refs/heads/devel/foo or
refs/users/someone/heads/foo. Our naming conventions mean that all
branches in refs/heads/ should be called master, devel/something or
releases/something. But it's easy for someone to get a "git push" command
wrong so that it would create a badly named branch.
Joseph S. Myers