bug-findutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Several changes made to fts.c in Gnulib


From: James Youngman
Subject: Re: Several changes made to fts.c in Gnulib
Date: Thu, 27 Jul 2017 12:23:11 +0100

Looking at the patch, it looks not terribly burdensome to maintain
"downtream" except for the possibility that some fts option could
subsequently be introduced in gnulib which shares a value with
FTS_NOLEAF.

Paul, since you don't plan to apply this patch upstream, do you have
any suggestions for ensuring that we avoid collision or maintenance
problems with the downstream patch?

James.

On Wed, Jul 26, 2017 at 9:22 PM, Kamil Dudka <address@hidden> wrote:
> On Wednesday, July 26, 2017 09:31:47 Paul Eggert wrote:
>> Kamil Dudka wrote:
>> > You even admitted that they could have introduced new bugs.  Now you are
>> > refusing to push a tiny commit that would significantly help to debug them
>> > in environments where only binaries are available.
>>
>> My changes fixed some bugs and did not affect the fts API. Your changes
>> would complicate the API, and this complexity is the principal objection.
>
> The API complexity is increased exactly by one bit.  If it is such a big
> problem for upstream maintainers, I will continue to maintain this added
> complexity myself.  It has been maintained in Fedora since December 2015
> with zero manpower spent on it so far.
>
> Kamil
>



-- 
--
This email is intended solely for the use of its addressee, sender,
and any readers of a mailing list archive in which it happens to
appear.   If you have received this email in error, please say or type
three times, "I believe in the utility of email disclaimers," and then
reply to the author correcting any spellings (and, optionally, any
incorrect spellings), accompanying these with humorous jests about the
author's parentage.   If you are not the addressee, you are
nevertheless permitted to both copy and forward this email since
without such permissions email systems are unable to transmit email to
anybody, intended recipient or not.  To those still reading by this
point, the author would like to apologise for being unable to maintain
a consistent level of humour throughout this disclaimer.  Contents may
settle during transit.  Do not feed the animals.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]