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

Previous Next

Full log

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

From: Tomas Volf <~@wolfsden.cz>
To: Liliana Marie Prikler <liliana.prikler <at> gmail.com>
Cc: guix-devel <at> gnu.org, 75552 <at> debbugs.gnu.org, 45mg <45mg.writes <at> gmail.com>,
 help-guix <at> gnu.org, Felix Lechner <felix.lechner <at> lease-up.com>
Subject: Re: Non-committers can't keep authenticated forks updated
Date: Fri, 17 Jan 2025 19:59:17 +0100

[Message part 1 (text/plain, inline)]

Liliana Marie Prikler <liliana.prikler <at> gmail.com> writes:

>> All of these things discussed in this thread are technically
>> possible.  But I think that we all agree that the friction involved,
>> compared to just using my own fork with the patch applied, is much
>> larger, at least in my opinion.
> Yes, we can agree that this is your opinion.  We can even agree that
> there is more friction, but I'm not sure whether we agree on the value
> of "much".  But honestly speaking, the friction with contributing to
> upstream is much more a social one (too few people to review) than a
> technical one, and soft forks are a band aid that will likely burn you
> out even sooner the more you commit to them.

I do not know what the future holds, but introduction of my soft-fork is
form Fri Sep 15 16:18:25 2023 +0200, and I am of the opinion that it
saved me more work that is has cost me over the time.  But yes, as you
stated, this is just my opinion.

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)]

Previous Next

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