INCIDENT: "master" branch is currently broken

[Tsukasa OI]

I didn't because I wasn't sure whether this fix is obvious (even being a
write-after-approval committer) but... anyway, thanks!

I confirmed that the exact revert is performed
(tree 02129ebadb74e7d3f2430cf8221799ce186600e3).

Thanks,
Tsukasa

On 2023/08/02 20:07, Sam James wrote:
> 
> Tsukasa OI via Binutils <binutils@sourceware.org> writes:
> 
>> Hello all,
>>
>> Some of you might be noticed and yes, "master" branch of GNU Binutils is
>> currently broken, in an attempt to create real "Binutils 2.41 release"
>> commit on the repository.
>>
>> Nick and I worked on creating a commit corresponding real Binutils 2.41
>> release and I shared the detailed procedure to Nick (which I tested on
>> my environment).  This procedure should have occurred on the
>> "binutils-2_41" tag but... actually occurred on the master branch,
>> breaking the branch.
>>
>> Since no commits since commit 675b9d612cc5 ("2.41 Release sources") are
>> pushed yet, we can restore the original changes if we revert this commit
>> relatively easily.
>>
>> Running "git revert HEAD" on the current master (**until no one else
>> push a commit**) branch will create a default commit message **exactly**
>> looking like this (including the commit hash) and make sure that this
>> default commit message is correct:
>>
>>> Revert "2.41 Release sources"
>>>
>>> This reverts commit 675b9d612cc59446e84e2c6d89b45500cb603a8d.
>>
> 
> I've gone ahead and reverted this as it's an error with an obvious fix.
> 
> thanks,
> sam
> 
>