From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:470:142:3::10]:39788)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i9qsP-0002QN-4l
 for guix-patches@gnu.org; Mon, 16 Sep 2019 09:17:10 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i9qsI-0006DO-Tp
 for guix-patches@gnu.org; Mon, 16 Sep 2019 09:17:09 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:40591)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
 id 1i9qsI-0006DC-FP
 for guix-patches@gnu.org; Mon, 16 Sep 2019 09:17:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
 (envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1i9qsI-00034i-7r
 for guix-patches@gnu.org; Mon, 16 Sep 2019 09:17:02 -0400
Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism
Resent-Message-ID: <handler.37413.B37413.156863980511793@debbugs.gnu.org>
References: <20190915221021.4165-1-ludo@gnu.org> <871rwgr3ib.fsf@elephly.net>
 <87r24g8khp.fsf@gnu.org>
From: Ricardo Wurmus <rekado@elephly.net>
In-reply-to: <87r24g8khp.fsf@gnu.org>
Date: Mon, 16 Sep 2019 15:16:29 +0200
Message-ID: <87woe8pej6.fsf@elephly.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
List-Id: <guix-patches.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-patches>
List-Post: <mailto:guix-patches@gnu.org>
List-Help: <mailto:guix-patches-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-patches>,
 <mailto:guix-patches-request@gnu.org?subject=subscribe>
Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org
Sender: "Guix-patches" <guix-patches-bounces+kyle=kyleam.com@gnu.org>
To: Ludovic =?UTF-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: 37413@debbugs.gnu.org


Hi Ludo,

> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> Ludovic Court=C3=A8s <ludo@gnu.org> writes:
>>
>>> It=E2=80=99s a bit weird to refer to commits from within a file in the =
repo
>>> 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 req=
uire
>> 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?

No, I actually meant for releases.  For a channel it seems to me that a
release would make sense whenever information must be displayed to the
users (presumably to announce breaking changes).

--
Ricardo