From: Sam James <sam@gentoo.org>
To: Mark Wielaard <mark@klomp.org>
Cc: Sam James via Overseers <overseers@sourceware.org>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: binutils-cvs and binutils-bugs lists
Date: Fri, 22 Mar 2024 11:30:14 +0000 [thread overview]
Message-ID: <87sf0izepl.fsf@gentoo.org> (raw)
In-Reply-To: <20240322111936.GS8319@gnu.wildebeest.org> (Mark Wielaard's message of "Fri, 22 Mar 2024 12:19:36 +0100")
Mark Wielaard <mark@klomp.org> writes:
> Hi Sam,
>
> On Fri, Mar 22, 2024 at 08:28:46AM +0000, Sam James via Overseers wrote:
>> For a while now, I've been wishing a binutils-cvs (or binutils-commits,
>> whatever) list existed.
>>
>> It turns out one did exist [0] but it's had no non-spam messages since
>> 2022-08-15. Was that intentional or did a hook just break at some point
>> so it stopped getting notifications?
>
> The pipermail archive still is getting updates:
> https://sourceware.org/pipermail/binutils-cvs/
>
> I think the issue is that mail is sent to bfd-cvs@sourceware.org.
> That addressis rejected by inbox.sourceware.org (but seems to have a
> special exception in mailman). So after the original import no new
> messages (except some spam) have been added.
>
> I filed https://sourceware.org/bugzilla/show_bug.cgi?id=31529
> We should import the rest and add an alias (and/or change the mail
> sending setup).
Ah, thanks! That must have been there I'd seen it in the past, but since
moved to public-inbox for all my viewing.
>
>> Also, while we're at it, does anyone object to a binutils-bugs list,
>> like gdb-prs, and gcc-bugs?
>
> binutils uses https://lists.gnu.org/archive/html/bug-binutils/
Could that possibly be added to inbox.s.o?
>
>> [0] https://inbox.sourceware.org/binutils-cvs/ [1]
thanks,
sam
next prev parent reply other threads:[~2024-03-22 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 8:28 Sam James
2024-03-22 11:19 ` Mark Wielaard
2024-03-22 11:30 ` Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-22 8:18 Sam James
2024-04-09 10:23 ` Nick Clifton
2024-04-10 13:59 ` Mark Wielaard
2024-04-10 14:01 ` Mark Wielaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf0izepl.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=binutils@sourceware.org \
--cc=mark@klomp.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).