Re: bug#7529: Bug#605639: deal better with different filesystem timestamp resolutions

On 12/03/10 02:03, Jim Meyering wrote: > Would you mind adding a "Bug fixes" entry for this > in coreutils' NEWS file? It'd be nice to commit that > along with an update of the gnulib submodule to the latest. Sure, done, with this notice: cp -u no longer does unnecessary copying merely becaus

nproc -> LGPL

Hello! I’d like to use ‘nproc’ in libguile, which is LGPLv3+. Could you change the license accordingly? Thanks, Ludo’.

Re: bug#7529: Bug#605639: deal better with different filesystem timestamp resolutions

Paul Eggert wrote: > Good eye! Thanks for the bug report and example. I installed > the following one-byte patch into gnulib; please give it a try. > It should propagate into coreutils the next time coreutils > updates from gnulib. > > A test case for this would require two file systems, one with

Re: gnulib and threaded execution

Ben Pfaff wrote: > > I would find it useful and systematic if we started to add a > > section "Multithreading:" to the module descriptions. ... > > The individual function descriptions in the manual might be a > good place to document where the thread-safety of a function > departs from that imple

Re: gnulib and threaded execution

Jim Meyering wrote: > > 2. because the alloca.c code assumes that there is a "stack > > direction". This is not the case any more with GCC's new > > "split stacks" . > > Is #2 really relevant? > alloca.c is compiled with gcc only for 1.x versions.