public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Form to subscribe to gdb mailing lists
Date: Mon, 11 May 2020 12:10:43 -0400	[thread overview]
Message-ID: <1efb693a-9bcd-b5d7-231f-ba9660721a43@polymtl.ca> (raw)
In-Reply-To: <20200511154419.GG4174@adacore.com>

On 2020-05-11 11:44 a.m., Joel Brobecker wrote:
> Hi Simon,
> 
>> It has been reported [1] that the form on the following page to subscribe to mailing lists is broken,
>> probably due to the recent infrastructure changes:
>>
>> https://www.gnu.org/software/gdb/mailing-lists/
>>
>> I propose that:
>>
>> 1. We remove this form
>> 2. We change the mailing list links to point to the "listinfo" links, where people can register
>>
>> For example, that means changing the "gdb" link from
>>
>>   https://sourceware.org/pipermail/gdb/
>>
>> to
>>
>>   https://sourceware.org/mailman/listinfo/gdb
>>
>> The first link leads to the archives, but the listinfo page has a link
>> to the archives, so it's not lost.
> 
> Sounds good to me.
> 
> Would you like me to take care of making the changes?

Ultimately, I think you are the one managing the website?  I don't mind
doing the work and sending you a patch if you point me to the right place.

Simon

  reply	other threads:[~2020-05-11 16:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11  4:06 Simon Marchi
2020-05-11 15:44 ` Joel Brobecker
2020-05-11 16:10   ` Simon Marchi [this message]
2020-05-11 16:21     ` Joel Brobecker
2020-05-11 17:16       ` Simon Marchi
2020-05-11 23:12 ` Joel Brobecker
2020-05-11 23:46   ` Simon Marchi
2020-05-12 18:45     ` Joel Brobecker

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=1efb693a-9bcd-b5d7-231f-ba9660721a43@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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).