From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/31393] Subscription email for libc-alpha not arriving.
Date: Fri, 16 Feb 2024 19:40:02 +0000 [thread overview]
Message-ID: <bug-31393-14326-jftDlNf8nD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31393-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31393
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Mark Wielaard from comment #1)
> Could you provide a bit more details so that we can track what is happening?
>
> What exactly was in the libc-alpha-owner email (any bounce or error message?)
> Which address did you try to subscribe?
I subscribed to libc-alpha using the standard mailman web form here:
https://sourceware.org/mailman/listinfo/libc-alpha
> How did you try to subscribe this address (email or webform)?
Normal mailman 2.x webform from the listinfo.
> As a workaround you can also subscribe people by hand at
> https://sourceware.org/mailman/admin/libc-alpha/members/add
Correct, and since I'm the list owner I can help them subscribe, but I filed
this for the broader issue that the confirmation email hasn't arrived at my
address yet either.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-02-16 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 17:58 [Bug Infrastructure/31393] New: " carlos at redhat dot com
2024-02-16 19:06 ` [Bug Infrastructure/31393] " mark at klomp dot org
2024-02-16 19:40 ` carlos at redhat dot com [this message]
2024-02-16 20:33 ` mark at klomp dot org
2024-02-16 20:46 ` carlos at redhat dot com
2024-02-16 21:05 ` mark at klomp dot org
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=bug-31393-14326-jftDlNf8nD@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@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).