From: Sam James <sam@gentoo.org>
To: "binutils@sourceware.org" <binutils@sourceware.org>
Cc: overseers@sourceware.org
Subject: binutils-cvs and binutils-bugs lists
Date: Fri, 22 Mar 2024 08:28:46 +0000 [thread overview]
Message-ID: <871q821xhd.fsf@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 484 bytes --]
[resending with fixed To:, sorry]
Hi all,
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?
Also, while we're at it, does anyone object to a binutils-bugs list,
like gdb-prs, and gcc-bugs?
[0] https://inbox.sourceware.org/binutils-cvs/ [1]
thanks,
sam
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next reply other threads:[~2024-03-22 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-22 8:28 Sam James [this message]
2024-03-22 11:19 ` Mark Wielaard
2024-03-22 11:30 ` Sam James
-- 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=871q821xhd.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=binutils@sourceware.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).