On Tue, 3 Aug 2021, Martin Liška wrote:
> On 8/2/21 7:22 PM, Joseph Myers wrote:
>
> Hey.
>
> > Some time ago, someone added a git symbolic-ref for refs/heads/trunk
> > pointing to refs/heads/master.
>
> Great you found out what caused that. We were aware of commits that didn't
> pass gcc-verif
On 8/3/21 12:03 PM, Aldy Hernandez wrote:
On 8/3/21 9:33 AM, Martin Liška wrote:
On 8/2/21 7:22 PM, Joseph Myers wrote:
Hey.
Some time ago, someone added a git symbolic-ref for refs/heads/trunk
pointing to refs/heads/master.
Great you found out what caused that. We were aware of commits t
On 8/3/21 9:33 AM, Martin Liška wrote:
On 8/2/21 7:22 PM, Joseph Myers wrote:
Hey.
Some time ago, someone added a git symbolic-ref for refs/heads/trunk
pointing to refs/heads/master.
Great you found out what caused that. We were aware of commits that didn't
pass gcc-verify check but for s
On 8/2/21 7:22 PM, Joseph Myers wrote:
Hey.
Some time ago, someone added a git symbolic-ref for refs/heads/trunk
pointing to refs/heads/master.
Great you found out what caused that. We were aware of commits that didn't
pass gcc-verify check but for some reason went in.
A side effect of thi
Some time ago, someone added a git symbolic-ref for refs/heads/trunk
pointing to refs/heads/master.
A side effect of this was to introduce a loophole in the checks run via
commit hooks, some of which are configured to apply only to master and
release branches and didn't apply if commits were pu
