From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jim Porter Newsgroups: gmane.emacs.bugs Subject: bug#62509: 30.0.50; Changes to naming for Windows stapshots - PATCH Date: Tue, 12 Sep 2023 21:14:34 -0700 Message-ID: <5c566017-59cd-99c8-b564-8ccedda795c2@gmail.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23442"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 62509@debbugs.gnu.org To: Corwin Brust , Stefan Kangas Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 13 06:15:16 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qgHHY-0005wC-0E for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 13 Sep 2023 06:15:16 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qgHHH-0003dz-9c; Wed, 13 Sep 2023 00:14:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qgHHF-0003dr-IH for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2023 00:14:57 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qgHHF-0000wK-Aj for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2023 00:14:57 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qgHHK-0005KP-0O for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2023 00:15:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jim Porter Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Sep 2023 04:15:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62509 X-GNU-PR-Package: emacs Original-Received: via spool by 62509-submit@debbugs.gnu.org id=B62509.169457849020447 (code B ref 62509); Wed, 13 Sep 2023 04:15:01 +0000 Original-Received: (at 62509) by debbugs.gnu.org; 13 Sep 2023 04:14:50 +0000 Original-Received: from localhost ([127.0.0.1]:60480 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qgHH8-0005Jj-55 for submit@debbugs.gnu.org; Wed, 13 Sep 2023 00:14:50 -0400 Original-Received: from mail-pl1-x62f.google.com ([2607:f8b0:4864:20::62f]:50553) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qgHH4-0005JV-Ee for 62509@debbugs.gnu.org; Wed, 13 Sep 2023 00:14:49 -0400 Original-Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1c09673b006so44522745ad.1 for <62509@debbugs.gnu.org>; Tue, 12 Sep 2023 21:14:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1694578475; x=1695183275; darn=debbugs.gnu.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=jhVj9jpfKDzRvNnWI38f1jyN8QCHs7zodCtwGCaY+r4=; b=sGqGS9LUyI6m+GrdeZVJWGhioKByx7HBpSf1uV3JTz8kX/xboH7EzDDqTF1hnkL4vu g1F3ODAgYCWZUFjaPxdeVt2/F0qbp5wT70pm18t6g98v1x70zoZ0rP0PG3boxCGFE7K7 pLFzdBbQbqZ3iLbY5TibuSwd/TLPw9tnIhPQBl2KObExOwVSiP6I1A6Hce7FZVuE7WvC EemiZD7x8rs7nY+KgtYR1qX2nk+ma916uCWY6Fg2hvKP9DD0wWMWBynYClb0yKPxncAF n2Rz8DsV4EVfRNMpbTgiXJI2WRRimWXWu/3caEbxmVCdztmcvqJaX8gxYUYnKq3Pa6Bu 5eIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694578475; x=1695183275; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=jhVj9jpfKDzRvNnWI38f1jyN8QCHs7zodCtwGCaY+r4=; b=IndoouW1ycxuhwZtO6DCFxgQQHOCd8sLREtUyxci2Du1wFDgQY+Ptj7H0Z+Xrhs2n5 v2KPjpIf+4FTxUBWctIQ5a+K3yKFS+Zz9hINagn8L26YB7goQS2Co0Vjs0c8es0qU8ua KQE/3qtgmt81YH3eoGgIIz7tNOgaYxC8uFqZ1foZvAHA3xu4A1FLs9VBU0+k9hG21y60 hRikafaxKwDGqJPh0wmKVRJcpufQmRMVNGQ3kIorJdxvS9PB4Ido77Jj+/cEUaS0KHM9 t52zKa4aRw6JGSES1ercH98hZgklOLymmii0L7y0IUCO+pWKH9PrR+Vvf3jOGb5gnYOB CMgw== X-Gm-Message-State: AOJu0YxJXMZTM8QSxIwZ3+EhcvYlIjq+sUL6ZVd1QysmkrAuLEhewpJQ v3URmg0phh1etm7MUqWm7wk= X-Google-Smtp-Source: AGHT+IEdnppVh+i9j2EAfcX3ggRuOY1hRMvP2T7SPY1SCOlgJFYnI+9OpSwQVAEs035WiAfPcQ5qyQ== X-Received: by 2002:a17:902:ea06:b0:1c3:eb95:2d27 with SMTP id s6-20020a170902ea0600b001c3eb952d27mr566879plg.48.1694578475452; Tue, 12 Sep 2023 21:14:35 -0700 (PDT) Original-Received: from [192.168.1.2] (cpe-76-168-148-233.socal.res.rr.com. [76.168.148.233]) by smtp.googlemail.com with ESMTPSA id c5-20020a170902d90500b001b9ecee459csm9221717plz.34.2023.09.12.21.14.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Sep 2023 21:14:35 -0700 (PDT) Content-Language: en-US In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:270246 Archived-At: On 9/12/2023 7:33 PM, Corwin Brust wrote: > From my standpoint, it is challenging to pick the date to use. I do > most releases for GNU rather manually, and might take a day or two > doing it. Is there information to be gained from knowing the "build > start date" (but not time?) that isn't better sourced by git log > ? I think so, yes. For those of us close to the development process, the Git SHA is the most-useful bit of info for sure, but thinking back to a couple of years ago before I contributed to Emacs, the date would have been a lot more useful. It would let me see at a glance how new the snapshot is. It would also make it easier to tell users what snapshot to try, e.g. if you're a package author: "Make sure you use the Emacs snapshot from at least YYYY-MM-DD in order to prevent such-and-such bug." The timestamp of the file itself isn't as useful for this purpose since, as you say, the process is a bit manual and could be a few days after the latest commit. As for what date exactly to use, I'd say, "Use the CommitDate in either US Eastern time (the FSF's time zone), or possibly UTC."