GNU bug report logs - #75552
Non-committers can't keep authenticated forks updated

Previous Next

Package: guix;

Reported by: 45mg <45mg.writes <at> gmail.com>

Date: Tue, 14 Jan 2025 04:23:02 UTC

Severity: normal

Full log


Message #35 received at 75552 <at> debbugs.gnu.org (full text, mbox):

From: Tomas Volf <~@wolfsden.cz>
To: Ricardo Wurmus <rekado <at> elephly.net>
Cc: 75552 <at> debbugs.gnu.org, 45mg <45mg.writes <at> gmail.com>,
 Liliana Marie Prikler <liliana.prikler <at> gmail.com>, help-guix <at> gnu.org,
 Felix Lechner <felix.lechner <at> lease-up.com>, guix-devel <at> gnu.org
Subject: Re: Non-committers can't keep authenticated forks updated
Date: Thu, 16 Jan 2025 15:15:16 +0100
[Message part 1 (text/plain, inline)]
Ricardo Wurmus <rekado <at> elephly.net> writes:

> Liliana Marie Prikler <liliana.prikler <at> gmail.com> writes:
>
>>> This has the slight issue that I can no longer easily answer a
>>> question "is this commit in my fork", since I cannot search by the
>>> commit hash. I admit it is not a question I need to answer often
>>> (last time was on 21st of October, CVE-2024-52867).
>> You could solve this by embedding an "upstream-commit:" trailer, but
>> that is an admittedly cursed transformation that no longer maps to a
>> single rebase, I admit.
>
> You can use the Change-Id tag for this.  Our local hooks create them and
> they stay intact after rebase.

Oh, right.  That was not a thing yet when I started my tree, but these
days it would work (with the obvious detail that people use commit
hashes, not change-ids, in emails, so I would need to translate first).

But yes, it still is large improvement over matching commit messages.

Tomas

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 175 days ago.

Previous Next


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