From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id WV2aI/NxsWp4EC4AWB0awg (envelope-from ) for ; Mon, 21 Sep 2026 14:05:39 -0400 Received: by simark.ca (Postfix, from userid 112) id 8E7BE1E051; Mon, 21 Sep 2026 14:05:39 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED, RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [38.145.34.32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id E8B971E01F for ; Mon, 21 Sep 2026 14:05:38 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 33E844B9DB45 for ; Mon, 21 Sep 2026 18:05:38 +0000 (GMT) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTP id 08B2C4BA2E0D for ; Mon, 21 Sep 2026 17:59:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 08B2C4BA2E0D ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 08B2C4BA2E0D ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1790013551; cv=none; b=vPoF4MHdZQF/qGah73QpTv4UI7Y4PlCjQD2EzumNMhAJnT3Lsm2ZO+o1nFYjJcn2DDCkqVtLE0AH+/VI4WW4VuHZEX3Mpbua51RqvSvNIsfiE5PgamftwuEu+bCh64ohwSYG+Awdlz2he1EZeijpBdvik72EadddJljPhVD6olE= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1790013551; c=relaxed/simple; bh=e63DtgqU4ekVMhp6QB26RqWdDCzKeLmpNddffVl30pg=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=DMJjoeQMIeRiaYFmisrsoPvmRvNmPqUNe7toTaAOoadQunZVEh8u/BTbnaIGoe0WHjeXLi2UejdL1CiMcAB65w1OndLkNhbB4jwcY7aIdMXYDoE/id9WdPs+FruKdZr6Dqn1mXD9gjPsmvNtHhd4+CldFUDLTWrkZsXCMqwcbpo= ARC-Authentication-Results: i=1; sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=edUEz4bc DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 08B2C4BA2E0D Received: from mail-qv1-f70.google.com (mail-qv1-f70.google.com [209.85.219.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-655-nnO2wTArNqCyCcqNpLtS3w-1; Mon, 21 Sep 2026 13:59:09 -0400 X-MC-Unique: nnO2wTArNqCyCcqNpLtS3w-1 X-Mimecast-MFC-AGG-ID: nnO2wTArNqCyCcqNpLtS3w_1790013549 Received: by mail-qv1-f70.google.com with SMTP id 6a1803df08f44-90cddf4f59eso66246866d6.3 for ; Mon, 21 Sep 2026 10:59:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1790013549; x=1790618349; h=content-transfer-encoding:content-type:cc:to:subject:message-id :date:from:in-reply-to:references:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=dA5OHzsD+m2/SECQqBBidMuxTaSI9Lvnvz5dAuuqW7A=; b=tKMWCBrnB8yEIxGAPsFEDNJiStC/NQyCVaBuUfz4AhKnSRW2smjTLGcngjT5i5/tlj ACYj3Gp0Qi2tlMvQVtc9vptDBZ5I9TjoItDJDpv5IF8y5UH3wt3n7CD8dOyi0Utet5lh CMU+VmN9O8VfknjRsh5uDHdsc10DUnfbvFexuBvS8iaBgb00QKGgTZfkzocGglAHGE5K V6z8mXK8mTAHMOdey3EMEVbdef9zHDpvxX+Ic+rdYyS2wsRqD0jcfwXs95qidb9yL4Py xTI0/62NsSfSvq8EJCknxXXk+Duwc41dfJhVxKrMdULH6hNfBdMPwhlR3NpqTGpHkOKB PJ/Q== X-Forwarded-Encrypted: i=1; AKwUvByM2AMp6faAvK08B8aFPZWYX8NvJvRwxnzt6W8qCx+mIyKcuV6j6fbZneFhXKJJDRsL5Hc=@sourceware.org X-Gm-Message-State: AFuF++kLTc1L/y16ybVwbfCqrks4oS/c4sH1HDrCebwmtc+gWFm9SO8z RnV77eaunu+eQkUzyCjxRSfge9b5IgXZEVtJc9+JFn4/SHgmuDfIS9l17HSOIzbMmFl8Rz3SoZG bZhVVmoSOhdZ8ZOkVc8ujv0Fy8jTKY12BLjRmxj3gcONI+IcCTzlEi0CSqInaGvp8RLbXQqlq4u onUQLR8mD1cML0wYIdHcSx31WCntI= X-Gm-Gg: AYBFou0ryl+sOmtAWcT3u8gcFIwj/WlhjcB+VJnOK+itV1TCfEiQYrroHvGybzB0PKV 6ZRR7gNTHraSVYxA++HpHd8kKGtyUwVuac8ipvMC9J/gXpUUtFofaD4d671PwL72xHHdNctlyl+ jbZod9ejE+FfUWFTRYaQXWUJAXsoj1RYde+FgSDW2d+jwfNSffIalIVjaG X-Received: by 2002:a05:620a:414e:b0:93a:5d6:9ef2 with SMTP id af79cd13be357-93c15e7afc8mr161671785a.36.1790013548599; Mon, 21 Sep 2026 10:59:08 -0700 (PDT) X-Received: by 2002:a05:620a:414e:b0:93a:5d6:9ef2 with SMTP id af79cd13be357-93c15e7afc8mr161668085a.36.1790013548004; Mon, 21 Sep 2026 10:59:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Mon, 21 Sep 2026 13:58:56 -0400 X-Gm-Features: AcwNN1U6QCaZAuxQ0Tl1n9q3x156SNFoH983uJmLu_rNpUI1nw8WheAHJwM4fcg Message-ID: Subject: Re: Meeting Minutes - Office Hours for CTI - 2026-09-18 To: Andrea Pinski Cc: "Carlos O'Donell" , gcc developers , glibc developers , gdb developers , binutils developers X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: 7y_8Px_9rQm6Xk-UR21lzn-_hp-auXAIQcmYd73SYZQ_1790013549 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: DJ Delorie via Gdb Reply-To: DJ Delorie Errors-To: gdb-bounces~public-inbox=simark.ca@sourceware.org Sender: "Gdb" On Mon, Sep 21, 2026 at 1:12=E2=80=AFPM Andrea Pinski via Gdb wrote: > > * Discuss on libc-alpha finalizing git URLs > > * git.glibc.coretoolchain.dev/glibc (RO mirror) > > * gitolite.glibc.coretoolchain.dev/glibc (RW for developers) > > * gitolite.glibc.coretoolchain.dev/glibc-keyring (RW for admins) > > What is the rationale for having 3 different URLs? The first is a general public-access git tree like everyone else uses. The second is a way to integrate remote git work (i.e. on your pc) with the master repository. It replaces login-style SSH as a way to "git push" with a key-based style. I've used it before and it's much easier to use and manage than raw git repos with SSH logins, and does not require that contributors have a login account on the git host. The third is the "management interface" for gitolite. The alternative to gitolite is to use a fork-and-pullrequest model (like gitlab, requires a web interface) or continue using login accounts. Having the developer repo separate from the public repo helps isolate the developers from the AI scraperbots, as the public one could be redirected through a CDN. > What is the rationale for using `coretoolchain.dev` rather than > something more specific named with gnu? Meh? Are ALL the core toolchain bits part of the GNU project? Will they always be? Do we want to be GNU snobs? ;-) > Why have a glibc subdomain? To make room for gcc.*, binutils*, gdb.*, etc. > > * Discuss on libc-alpha finalize mailing list names: > > * Place mailing list services under lists.glibc.coretoolchain.dev > > * glibc-announce@lists.glibc.coretoolchain.dev > > * glibc-devel@lists.glibc.coretoolchain.dev > > * glibc-stable@lists.glibc.coretoolchain.dev > > * glibc-testresults@lists.glibc.coretoolchain.dev > > * glibc-help@glibc.lists.glibc.coretoolchain.dev > > * glibc-vcs@lists.glibc.coretoolchain.dev > > Especially here about why not just have lists.coretoolchain.dev rather > than have a glibc subdomain. Plus isn't glibc on the mailing list > name and the domain redundant? This assumes that all projects want to have their project name in their mailing list names. For example, gcc might want "patches@lists.gcc.*" or "patches@gcc.*" I would not be opposed to renaming our mailing lists to be "foo@glibc.*" instead of "glibc-foo@.*" if we're moving them *at all*. I don't think we need the "lists." part in the mailing list name - MX records can redirect glibc.* to lists.glibc.* unless there are technical reasons to not send local non-list mail (there shouldn't be any IMHO) through the list server host.