Re: Mailing list bpf@gcc.gnu.org

Re: Mailing list bpf@gcc.gnu.org

[Jose E. Marchesi]

> Hi Jose,
>
> On Tue, Jan 27, 2026 at 09:16:18AM +0100, Jose E. Marchesi wrote:
>> 
>> Gentle re-ping :)
>
> Finally created. And added documentation on how to create such lists:
> https://sourceware.org/sourceware-wiki/EmailNewMailmanList
>
> Could you update https://gcc.gnu.org/lists.html
> https://gcc.gnu.org/cgit/gcc-wwwdocs/tree/htdocs/lists.html

Just pushed a patch for that.
Thank you! :)

> Thanks,
>
> Mark
>
>> >> Hi Jose,
>> >>
>> >> On Wed, Jan 14, 2026 at 12:05:55AM +0100, Jose E. Marchesi via Overseers wrote:
>> >>> 
>> >>> gentle ping
>> >>> 
>> >>> Is there anything else e should do to get the list created?
>> >>
>> >> No, sorry. I thought I should take this oppertunity to write a manual
>> >> for adding new mailinglists, assigning moderators, how to set them up
>> >> for From rewriting (or not) and how to hook it up to
>> >> inbox.sourceware.org (which will soon change when public-inbox goes
>> >> into its own VM), etc. So then it suddenly felt like work...
>> >
>> > Oh very nice :)
>> >
>> >> So should this list use From-rewriting or not? If it is a patches list
>> >> then I would recommend not to mangle any headers so git am works and
>> >> b4 can inspect the dkim headers. But some people prefer From-rewriting
>> >> to combat bad dmarc/dkim setups.
>> >
>> > I think we can try with no header mangling first.  I use git am all the
>> > time..
>> >
>> > Thanks!
>> >
>> >>
>> >>> Thanks!
>> >>> 
>> >>> > Hello overseers!
>> >>> >
>> >>> > Looks like nobody objects to having a list bpf@gcc.gnu.org for GCC BPF
>> >>> > development [1].  Could we please get it created?
>> >>> >
>> >>> > As description for the list we could use:
>> >>> >
>> >>> > "Compiled BPF discussion in general and BPF GCC backend in particular."
>> >>> >
>> >>> > It would be good if me and David Faust (who is a reviewer for the BPF
>> >>> > backend in GCC) would be set as maintainers of the list.
>> >>> >
>> >>> > Thank you, you are the best! :)
>> >>> >
>> >>> > [1] https://gcc.gnu.org/pipermail/gcc/2026-January/247324.html