From: Christopher Faylor <cgf-use-the-mailinglist-please@gcc.gnu.org>
To: Bryan Hundven <bryanhundven@gmail.com>
Cc: crossgcc maillist <crossgcc@sourceware.org>,
Alexey Neyman <aneyman@lynx.com>,
Chris Packham <judge.packham@gmail.com>,
"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: Unsubscribe problems apparently solved
Date: Sun, 30 Aug 2020 17:16:29 -0400 [thread overview]
Message-ID: <20200830211629.GA6073@cgf.cx> (raw)
In-Reply-To: <CAJ+oik0d4jHsqh9p-U0sORQ2gWHQ2nUmmHzXpWGN+t1QgNTQ9w@mail.gmail.com>
On Sun, Aug 30, 2020 at 01:38:38PM -0700, Bryan Hundven wrote:
>Christopher,
>
>(Sorry if I got CC emails wrong... it's been a while...)
>
>On Sun, Aug 30, 2020 at 1:19 PM Christopher Faylor <
>cgf-use-the-mailinglist-please@gcc.gnu.org> 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 sourceware.org.
>>
>> cgf
>> (20 year sourceware.org volunteer admin)
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>
>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 (
>http://jk.ozlabs.org/projects/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.
Not really sure we're talking about the same thing here. There are
already crosstool-ng prefixes being added by git. The mailing list is
sponsored by sourceware.org. No one really owns it. The unsubscribe
information is at the bottom of every message.
I wasn't complaining about the addition of "[crosstool-ng/crosstool-ng]" to
messages. It just was apparently a point of confusion.
next prev parent reply other threads:[~2020-08-30 21:16 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] ` <6a6fa59c33b41435f6f907739d7d88cc1a153f33.camel@silogroup.org>
[not found] ` <24cde6c4-20c8-a583-fdd0-508f8ebd4dd4@digitalsignallabs.com>
[not found] ` <dad569fca04a8fcb23449f6f1e9836b6d468e6d7.camel@silogroup.org>
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
2020-08-30 21:16 ` Christopher Faylor [this message]
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:
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=20200830211629.GA6073@cgf.cx \
--to=cgf-use-the-mailinglist-please@gcc.gnu.org \
--cc=aneyman@lynx.com \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=judge.packham@gmail.com \
--cc=yann.morin.1998@free.fr \
/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).