public inbox for
 help / color / mirror / Atom feed
From: Bryan Hundven <>
To: crossgcc maillist <>
Cc: "Yann E. MORIN" <>,
	Chris Packham <>,
	Alexey Neyman <>
Subject: Re: Unsubscribe problems apparently solved
Date: Sun, 30 Aug 2020 13:38:38 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


(Sorry if I got CC emails wrong... it's been a while...)

On Sun, Aug 30, 2020 at 1:19 PM Christopher Faylor <> wrote:

> Hi all,
> The two people for whom the unsubscribe instructions "did not work"
> apparently managed to follow the instructions and unsubscribe.
> Sorry for the noise.  You'd think that a technical mailing list wouldn't
> have these types of problems.
> Btw, the name of this mailing list is "crossgcc".  I don't know why
> something is adding "crosstool-ng" to the subject but it's not being
> done by
> cgf
> (20 year volunteer admin)
> --
> For unsubscribe information see

Personally, I do understand and appreciate your feedback.

From my understanding this mailing list started as a place to chat about
cross-compling GCC, and I do not know how or when crosstool-ng started
using this mailing list as a way to use patchwork ( to commit changes to crosstool-ng
(on an OSUOSL server using mercurial).

At a certain point (2011? 2012?), Yann E. Morin and I decided to move
contributing to crosstool-ng to github (from a mercurial repo). I'm sure
there is a way to somehow add `[crosstool-ng]` as a prefix to the subject
of Pull Requests and Merge notifications, I just don't know how. Maybe it
is time for us to stop notifying this mailing list of changes, and inform
developers to subscribe/like/follow the github repository. That way this
mailing list can continue to be a mailing list about talking about
cross-compling GCC.

As an admin, and co-contributor (well, not so much lately; as my work, my
daughter, and some things in my personal life have taken over), I would
like to know what we can do to make this mailing list what it should be. I
don't know who owns this mailing list, maybe we also need their help in
updating the (un)subscribe page so that it is clear on how to (un)subscribe
to this mailing list.

I want to help aid in what is best, but I don't want to dictate what
"should happen". Maybe others can provide some feedback?


-Bryan Hundven

  reply	other threads:[~2020-08-30 20:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30  8:59 [crosstool-ng/crosstool-ng] 107e81: Add support for glibc 2.32 Chris Packham
2020-08-30 14:16 ` Randy Yates
2020-08-30 16:57   ` Daniele Testa
2020-08-30 19:34     ` Christopher Faylor
2020-08-30 19:43       ` Daniele Testa
2020-08-30 19:58         ` Christopher Faylor
     [not found]   ` <>
     [not found]     ` <>
     [not found]       ` <>
2020-08-30 20:04         ` Randy Yates
2020-08-30 20:15           ` Andrea Franceschini
2020-08-30 20:19           ` Unsubscribe problems apparently solved Christopher Faylor
2020-08-30 20:38             ` Bryan Hundven [this message]
2020-08-30 21:16               ` Christopher Faylor
2020-08-30 21:20               ` Chris Packham
2020-08-30 23:06                 ` Christopher Faylor

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).