Follow-up Comment #4, bug #51841 (project findutils):
Thanks for the tests.
It seems they fail here:
-l1 1990-06-22+14:00:00.00 646056000.00 [...]
+l1 1990-06-22+12:00:00.00 646056000.00 [...]
The expected output for '%T+' depends on the local timezone.
As the nex
James Youngman wrote:
gnulib foliks, do you have test data which results in FTS_DC being
returned by fts_read? If not, have you tested in any other way that
ent->fts_cycle->fts_pathlen is in-bounds for this case?
The Gnulib tests for fts are minimal and don't use FTS_DC as far as I know.
I t
Follow-up Comment #4, bug #51926 (project findutils):
> It turns out that find treats "-xtype (anything)" as false on a
broken link, which doesn't seem to be specified in the manual page. So it
would be plausible to treat it as false on a circular link as well.
Not really:
$ ln -s nowhere broken
On Saturday, September 2, 2017 5:35:31 PM CEST James Youngman wrote:
> * gnulib-local/lib/fts.c.diff: incorporated from a patch by Kamil
> Dudka . This patch introduces an FTS_NOLEAF option
> to fts.
> * gnulib-local/lib/fts_.h.diff: Likewise.
> * find/ftsfind.c (ftsoptions): point out that is_fts
