From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Carlos O'Donell <carlos@redhat.com>
Cc: Overseers mailing list <overseers@sourceware.org>,
Alan Matsuoka <alanm@redhat.com>, Nick Clifton <nickc@redhat.com>
Subject: Re: A problem when trying to sign up for the binutils mailing list
Date: Mon, 21 Mar 2022 22:16:56 -0400 [thread overview]
Message-ID: <20220322021656.qxzyp43ognzhcpx2@cgf.cx> (raw)
In-Reply-To: <07dc061b-70dc-b3b4-84ea-2b4c99fb7975@redhat.com>
On Mon, Mar 21, 2022 at 11:00:47AM -0400, Carlos O'Donell wrote:
>On 3/21/22 10:50, Nick Clifton via Overseers wrote:
>> Hi Guys,
>>
>> Â A problem has been reported when trying to use the gnu.org binutils[1]
>>  web page to subscribe to a mailing list. The "Send in the request"
>> Â button results in a '404 not found' message.
>>
>> Â I checked the html for the page and it tries to initiate an action with:
>>
>> Â Â Â https://sourceware.org/cgi-bin/ml-request
>>
>> Â Looking in the cgi-bin directory I see that this script is no longer
>>  present. (Although a ml-request.orig and ml-request~ files are present).
>>
>> Â Has the feature been removed/deprecated, or should the ml-request still
>> Â exist ?
>
>There are other cgi-bin binaries we run on sourceware, but this particular
>one was not setup again after the last transition.
That particular one was ezmlm-only. We're a mailman shop now.
>For glibc I switched to linking directly the mailman listinfo page:
>
>e.g.
>http://www.gnu.org/software/libc/started.html
>
>[libc-announce] -> https://sourceware.org/mailman/listinfo/libc-announce/
>
>It avoids needing a cgi-bin to register mailing list requests and more
>directly exposes the user to our mailing lists which is good IMO since
>they can see the archive page, and set more parameters for their subscription.
Right. Just point to the right page for subscribing to the mailing list in question.
cgf
prev parent reply other threads:[~2022-03-22 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <rt-4.2.16-14-g9a593ee-783-1647871701-1880.1819623-8-0@rt.gnu.org>
2022-03-21 14:50 ` Nick Clifton
2022-03-21 15:00 ` Carlos O'Donell
2022-03-22 2:16 ` Christopher Faylor [this message]
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=20220322021656.qxzyp43ognzhcpx2@cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=alanm@redhat.com \
--cc=carlos@redhat.com \
--cc=nickc@redhat.com \
--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).