From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:37311) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i9qbt-0006qL-GQ for guix-patches@gnu.org; Mon, 16 Sep 2019 09:00:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i9qbr-0007O1-RC for guix-patches@gnu.org; Mon, 16 Sep 2019 09:00:05 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:40569) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i9qbr-0007Ly-Ap for guix-patches@gnu.org; Mon, 16 Sep 2019 09:00:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i9qbr-0002e0-2L for guix-patches@gnu.org; Mon, 16 Sep 2019 09:00:03 -0400 Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism Resent-Message-ID: From: Ludovic =?UTF-8?Q?Court=C3=A8s?= References: <20190915221021.4165-1-ludo@gnu.org> <871rwgr3ib.fsf@elephly.net> Date: Mon, 16 Sep 2019 14:59:46 +0200 In-Reply-To: <871rwgr3ib.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 16 Sep 2019 11:31:40 +0200") Message-ID: <87r24g8khp.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ricardo Wurmus Cc: 37413@debbugs.gnu.org Hello, Ricardo Wurmus skribis: > Ludovic Court=C3=A8s writes: > >> It=E2=80=99s a bit weird to refer to commits from within a file in the r= epo >> because it almost forces you to push so that you know the commit ID >> that your news entry should refer to. News entries become obsolete >> if you rebase, too. I think it=E2=80=99s acceptable, though. > > Would tags be acceptable instead of commit IDs? I think version tags > would be easier to deal with than commit IDs and it wouldn=E2=80=99t requ= ire > time travel as you can just make up a new version and refer to that in > the news file. So you would add a Git tag like =E2=80=9Cnews-xyz=E2=80=9D on the commit of= interest and then refer to it in the news entry? I guess that would work. Compared to this patch set, we=E2=80=99d just nee= d to check whether the entry=E2=80=99s commit is a commit or a tag, and in the l= atter case resolve it. How does that sound? I tend to use tags sparsely, almost exclusively for releases, so I would not naturally propose to use them for this purpose, but maybe it=E2=80=99s = not a problem to have many tags in the repo after all? Thanks, Ludo=E2=80=99.