From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) by sourceware.org (Postfix) with ESMTPS id 99D543857814 for ; Sun, 30 Aug 2020 20:38:49 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 99D543857814 Received: by mail-oi1-x233.google.com with SMTP id d189so5425444oig.12 for ; Sun, 30 Aug 2020 13:38:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xoe3vArKLesAx7sGT2LCPoGuXDnhmID4VNW0gvZv9PA=; b=G3EZFmHQ8B0xRLFVcOnA3D/eErRCsVHpEc9th+vCLjKi4BdwIYmnf3Zn/YmA33/BAg jqmYhWeUHYTEd5sT0X0gxtbpxPd/1h7Ul1CS+3Jxcbqj/nMwbj1MuUf2VNsK3Z4twTrm nscAHYzT3y1DRBUqGUmTiOQpd8jILPKmP+zlw7l1KzzaWNFHb+T+y6ifsoFOwqXp40HK J90NAB+NoloKCFvG4d1NOJIVvYlXjFhWGSqYLjcYnNg7mexqI7JLXcmtiwGHvZwo0Sis Bln/7ylU7XoHAEztYZJI90JEeZrsEmEGruwnOZTGyobt5WpiYltZ9eb5UteX8wcxHKKK 873Q== X-Gm-Message-State: AOAM531/AYk9etR91ZLLyz6OnI9hcFBZe34v+Ln5//8MoQ6fTWgnU593 rBtJYQyRR4eF2qvmiBlTb1fU7GZJ9hMFtKVcFKSjoU7ERltndA== X-Google-Smtp-Source: ABdhPJwczPzt1dwXF64oPkTgx6jblk8iFEylNWph+T8aeMf57IWhQVGo/38BkJ3eArPH7cQt/iZ2nqIgGZ4oKdPPMEA= X-Received: by 2002:aca:eb51:: with SMTP id j78mr1776299oih.169.1598819928839; Sun, 30 Aug 2020 13:38:48 -0700 (PDT) MIME-Version: 1.0 References: <23b151ff-e216-6a66-a3a5-9b8b5fe0bb82@digitalsignallabs.com> <6a6fa59c33b41435f6f907739d7d88cc1a153f33.camel@silogroup.org> <24cde6c4-20c8-a583-fdd0-508f8ebd4dd4@digitalsignallabs.com> <20200830201900.GA5707@cgf.cx> In-Reply-To: <20200830201900.GA5707@cgf.cx> From: Bryan Hundven Date: Sun, 30 Aug 2020 13:38:38 -0700 Message-ID: Subject: Re: Unsubscribe problems apparently solved To: crossgcc maillist Cc: "Yann E. MORIN" , Chris Packham , Alexey Neyman X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: crossgcc@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: crossgcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Aug 2020 20:38:51 -0000 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. 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? Sincerely, -Bryan Hundven