Re: utimens and non-standardized futimesat [was: coreutils-6.11-1 in release-2 area]

2008-05-29 Thread Eric Blake
Bruno Haible clisp.org> writes: > Two nits (I'm really only nitpicking): > > - You introduce two #ifs that have to be the same condition: > #if HAVE_FUTIMESAT || HAVE_WORKING_UTIMES > ... > #if HAVE_FUTIMESAT || HAVE_WORKING_UTIMES And only so that C89 compilation will work when you

Re: utimens and non-standardized futimesat

2008-05-29 Thread Jim Meyering
Eric Blake <[EMAIL PROTECTED]> wrote: > According to Eric Blake on 5/22/2008 6:51 AM: > | According to Jim Meyering on 5/22/2008 6:42 AM: > | |> |> No need to refer the dir by name: > | |> |> > | |> |> futimens (dirfd. timespec); > | |> | > | |> | Btw., even if you don't consider the Posix 200x f

Re: utimens and non-standardized futimesat [was: coreutils-6.11-1 in release-2 area]

2008-05-29 Thread Bruno Haible
Eric Blake wrote: > Tested on cygwin 1.7.0, where futimens and utimensat exist, and on cygwin > 1.5.25, where those and futimesat are all missing. OK to apply? This > means that coreutils can now support nanosecond resolution on new enough > kernels for things like touch and cp -p. Two nits (I'm

utimens and non-standardized futimesat [was: coreutils-6.11-1 in release-2 area]

2008-05-28 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 5/22/2008 6:51 AM: | According to Jim Meyering on 5/22/2008 6:42 AM: | |> |> No need to refer the dir by name: | |> |> | |> |> futimens (dirfd. timespec); | |> | | |> | Btw., even if you don't consider the Posix 200x funct