GNU bug report logs - #37413
[PATCH 0/9] Channel news distribution mechanism

Previous Next

Package: guix-patches;

Reported by: Ludovic Courtès <ludo <at> gnu.org>

Date: Sun, 15 Sep 2019 22:11:02 UTC

Severity: normal

Tags: fixed, patch

Done: Ludovic Courtès <ludo <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 37413 <at> debbugs.gnu.org
Subject: [bug#37413] [PATCH 0/9] Channel news distribution mechanism
Date: Mon, 16 Sep 2019 14:59:46 +0200
Hello,

Ricardo Wurmus <rekado <at> elephly.net> skribis:

> Ludovic Courtès <ludo <at> gnu.org> writes:
>
>> It’s 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’s 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’t require
> 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 “news-xyz” 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’d just need to
check whether the entry’s commit is a commit or a tag, and in the latter
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’s not a
problem to have many tags in the repo after all?

Thanks,
Ludo’.




This bug report was last modified 5 years and 295 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.