Branching this weekend

[Nick Alcock]

On 22 Jul 2024, Nick Clifton verbalised:

> Hi Maciej,
>
>>   I'm blocked on having correct authorship attribution provided for:
>> <https://inbox.sourceware.org/binutils/20230616072536.1805704-1-yunqiang.su@cipunited.com/>,
>> which I have a fixed version of ready to push, and which I want to see in
>> 2.43.  I guess this probably is not something that should prevent you from
>> branching unless you want to cut the release right away (which I gather is
>> not the case)
>
> Correct - I will be evaluating the branch for at least 2 weeks.

Presumably there's no objection to bugfixes and reversals of
in-hindsight-ill-advised changes made in trunk between the branch and
release? I have some libctf stuff coming up in the next day or so...

(Mostly bugfixes, but also one addition of a bit of API to make the
recent change to block addition of duplicate enumerators in enums an
opt-in feature instead of always-on, since horrifyingly existing
programs really do rely on this even though C obviously prohibits such
things in C itself. e.g. it turns out pahole can stuff duplicate
enumerators into the BTF it emits, and it turns out to hugely complicate
BTF->CTF converters for libctf to unequivocally ban it.)

-- 
NULL && (void)