Paul Eggert <[email protected]> writes: > On 2026-01-01 21:07, Collin Funk wrote: >> Pádraig, I assume this warrants a NEWS entry under "Bug Fixes"? > > It's just a performance improvement, no? And not such a big > improvement that it warrants being called aa "bug fix".
I was conflicted on that since it might be considered a bug in fts. I guess it worked fine though, just much slower. I pushed the attached patch to mention the improvement in NEWS. By the way Tim, the fts_* functions are a part of glibc as well. However, the inode sorting code is not contained there. I assume it was a gnulib invention among some other extensions we have, e.g., using openat() instead of chdir(). So no need for any changes there. I forgot to mention that in my previous mail. Collin
>From ae5ceffc1341463d0588ee982a32995338b09cad Mon Sep 17 00:00:00 2001 Message-ID: <ae5ceffc1341463d0588ee982a32995338b09cad.1767411498.git.collin.fu...@gmail.com> From: Collin Funk <[email protected]> Date: Fri, 2 Jan 2026 19:29:11 -0800 Subject: [PATCH] doc: NEWS: mention du performance improvement on the Lustre file system Reported by Tim Day <[email protected]> in <https://bugs.gnu.org/80106>. * NEWS: Mention the improvement after gnulib commit 578b8d7dc5. --- NEWS | 3 +++ 1 file changed, 3 insertions(+) diff --git a/NEWS b/NEWS index f5d3e3bec..e3858a855 100644 --- a/NEWS +++ b/NEWS @@ -62,6 +62,9 @@ GNU coreutils NEWS -*- outline -*- csplit, ls, and sort, now handle a more complete set of terminating signals. + 'du' now processes directories with 10,000 or more entries up to 9 times + faster on the Lustre file system. + 'pinky' will now exit immediately upon receiving a write error, which is significant when reading large plan or project files. -- 2.52.0
