From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTP id 8D931385803D for ; Thu, 14 Oct 2021 09:19:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8D931385803D Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-456-eEzcxqfzMhiZZiKoP2BMnA-1; Thu, 14 Oct 2021 05:19:48 -0400 X-MC-Unique: eEzcxqfzMhiZZiKoP2BMnA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BA3421006AA2; Thu, 14 Oct 2021 09:19:47 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.193.172]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 56C4F19D9F; Thu, 14 Oct 2021 09:19:47 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.16.1/8.16.1) with ESMTPS id 19E9Jiv12769876 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 14 Oct 2021 11:19:44 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.16.1/8.16.1/Submit) id 19E9Jg0o2769875; Thu, 14 Oct 2021 11:19:42 +0200 Date: Thu, 14 Oct 2021 11:19:42 +0200 From: Jakub Jelinek To: Tobias Burnus Cc: Martin =?utf-8?B?TGnFoWth?= , Jonathan Wakely , gcc-patches@gcc.gnu.org Subject: Re: [RFC] Port git gcc-descr to Python Message-ID: <20211014091942.GT304296@tucnak> Reply-To: Jakub Jelinek References: <7e803eb3-d9df-99de-490d-823c1ffe29d7@suse.cz> <20211008111246.GF304296@tucnak> <11400b93-b2bb-6133-88f7-20219433f2a7@suse.cz> <12d44ac0-8849-466c-9749-b4e1e7168ac7@suse.cz> <846ffa97-c2c4-2dd4-9d02-ed6db5d1ffa7@codesourcery.com> MIME-Version: 1.0 In-Reply-To: <846ffa97-c2c4-2dd4-9d02-ed6db5d1ffa7@codesourcery.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-5.5 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Oct 2021 09:19:55 -0000 On Thu, Oct 14, 2021 at 11:06:55AM +0200, Tobias Burnus wrote: > Additionally, I observe the following (independent of the conversion): > For 7433458d871f6bfe2169b9d7d04fec64bb142924, I get: > r0-80854-g7433458d871f6b > The question is whether we are happy that only reversions since > basepoints/gcc-5 have a version number or whether we want to > use releases/gcc-x.y.0 -> x.y as fallback when basepoint does not > exist or back-added more basepoints? Admittedly, this will add '.', > thus, maybe the answer is 'no'? Yes, everything older than basepoints/gcc-5 is r0-NNNNN-gNNNNNN by design. Digits aren't allowed there and while we could use say underscore, it doesn't seem to be worth it for such old history, and all the bugzilla highlighting, web redirection etc. handles just r number - number - g hexnumber or r number - number formats. It is more common to refer to the old commits through svn revisions anyway. Jakub