Re: pkgquilt

nia <[email protected]> writes:

> You're not forking them. Nobody is upstreaming patches to add
> GCC14 support and fix a recently-revealed segfault in a 
> Xlib application that last got a new version in 2003.

I suspect most of this sort of thing doesn't run into the motivation for
quilt.  It seemed to me that it was about carrying substantive patches
more than the usual build fixes.


I understand your frustration at dropped patches and I hope that hasn't
been me doing it more than once in a great while.

I, on the other hand, am not happy about when, in packages I maintain
and push the changes I make upstream, others commit patches, usually for
systems I don't have available for testing on, and don't file them
upstream.  Those patches then need to be conflict-resolved repeatedly -
by me when doing updates.  So those I am tempted to just drop.  This is
in the context of an upstream that is functioning reasonably.  Patches
to packages where there are no new releases don't need merging :-(.