public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Form to subscribe to gdb mailing lists
Date: Mon, 11 May 2020 16:12:29 -0700	[thread overview]
Message-ID: <20200511231229.GL4174@adacore.com> (raw)
In-Reply-To: <fd18815d-02b2-f15e-1531-43a105de8061@polymtl.ca>

Hi Simon,

On Mon, May 11, 2020 at 12:06:03AM -0400, Simon Marchi wrote:
> 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.

I've made the update.

Each mailing list entry looks like this, now:

   gdb-announce (archives)
        A read-only low volume list for the posting of announcements
        about releases or other important events.

"gdb-announce" is a link that points to the mailmain user interface
for that mailing-list.

"archives" is a link to the archives.

That way, we get both a link to the subscribe/unsubscribe and
the archives at the same time!

Normally, I tested every link, but let me know if missed something,
or misunderstood.

-- 
Joel

  parent reply	other threads:[~2020-05-11 23:12 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
2020-05-11 16:21     ` Joel Brobecker
2020-05-11 17:16       ` Simon Marchi
2020-05-11 23:12 ` Joel Brobecker [this message]
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=20200511231229.GL4174@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /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).