Re: new snapshot available: coreutils-7.5.76-1c0ec

2009-09-10 Thread Jim Meyering
Pádraig Brady wrote: > rerunning on local file systems: > >Passed Skipped Failed > \- > Fedora core 5 x86 | 348 42 0 > Fedora 11 x86 | 343 47 0 > Solaris 10 x86|

debian coreutils patches

2009-09-10 Thread Michael Stone
I'm attaching the current patches from the debian coreutils package to make sure they don't get missed. 61_whoips: this one will be problematic to include directly as I don't have the autoconf-fu to make the network functions portable to non-linux platforms, and the core function was pulled fro

Re: readlink(1) behavior

2009-09-10 Thread Eric Blake
Eric Blake byu.net> writes: > I'm not sure that there are that many clients of > canonicalize_file_mode outside of coreutils. Also, both canonicalize-lgpl and canonicalize mishandle leading //, when that is special. Which means 'readlink -f //machine/share' on cygwin incorrectly fails. --

Re: extend inotify to support file descriptors in addition to paths

2009-09-10 Thread Eric Paris
On Tue, Sep 8, 2009 at 8:21 PM, Giuseppe Scrivano wrote: > at the moment inotify permits to add new files to be watched using their > path.  There are situations where the file path is not know but a > descriptor is available.  It would be desiderable to have the > possibility to use the inotify

[PATCH] link, ln: use gnulib's link module to work around Solaris 10 deficiency

2009-09-10 Thread Jim Meyering
FYI, I've just pushed the following. It may be the final change before coreutils-7.6. >From ebc7aacf7b7115bf51305579aaa7ddce77301fd7 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Thu, 10 Sep 2009 17:51:44 +0200 Subject: [PATCH] link,ln: use gnulib's link module to work around Solaris 10 defi

Re: readlink(1) behavior

2009-09-10 Thread Eric Blake
Jim Meyering meyering.net> writes: > I'd just as soon put this off until after 7.6. Agreed; it involves gnulib changes, and it isn't worth holding up the current release to change any of this today. > Since this nit is in a corner of a tool isn't even specified > by POSIX, it seems ok to defer

Re: readlink(1) behavior

2009-09-10 Thread Jim Meyering
Eric Blake wrote: > I think there are some infelicities in the canonicalization options of > readlink. > > readlink -fv file/=> correctly reports ENOTDIR > readlink -fv missing => lists /path/to/missing > readlink -fv missing/ => complains that missing is not a dir > readlink -mv file/=>

readlink(1) behavior

2009-09-10 Thread Eric Blake
I think there are some infelicities in the canonicalization options of readlink. readlink -fv file/=> correctly reports ENOTDIR readlink -fv missing => lists /path/to/missing readlink -fv missing/ => complains that missing is not a dir readlink -mv file/=> lists /path/to/file readlink -mv

[PATCH] ln: use gnulib's link module, to work around Solaris 10 deficiency

2009-09-10 Thread Jim Meyering
Jim Meyering wrote: > Eric Blake wrote: >> According to Jim Meyering on 9/10/2009 6:24 AM: >>> >>> Currently, we're at gnulib (v0.0-2549-g2c90f1a) for the submodule. >>> None of the patches since then seemed to be essential to coreutils >>> on non-mingw/cygwin systems. Let me know if you'd like to

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Jim Meyering
Pádraig Brady wrote: > Jim Meyering wrote: >> Here's one more posssible wording: >> >> Display values are in units of the first available SIZE from --block-size, >> and the %s_BLOCK_SIZE, BLOCK_SIZE and BLOCKSIZE environment variables. >> Otherwise, it defaults to 1024 bytes (or 512 bytes if POSIXL

Re: [PATCH] dd conv=unblock: print final newline consistently

2009-09-10 Thread Jim Meyering
Eric Blake wrote: > According to Jim Meyering on 9/10/2009 6:24 AM: >> >> Currently, we're at gnulib (v0.0-2549-g2c90f1a) for the submodule. >> None of the patches since then seemed to be essential to coreutils >> on non-mingw/cygwin systems. Let me know if you'd like to use >> a newer version. >

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Pádraig Brady
Jim Meyering wrote: > Here's one more posssible wording: > > Display values are in units of the first available SIZE from --block-size, > and the %s_BLOCK_SIZE, BLOCK_SIZE and BLOCKSIZE environment variables. > Otherwise, it defaults to 1024 bytes (or 512 bytes if POSIXLY_CORRECT is set). Pushed

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Jim Meyering
Pádraig Brady wrote: > Eric Blake wrote: >> According to Pádraig Brady on 9/10/2009 6:29 AM: >>> While this patch is more verbose than my previous patch >>> in this thread, it is more accurate. So let's drop the >>> previous one. >> >>> + printf (_("\n\ >>> +If none of the environment variabl

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Jim Meyering
Eric Blake wrote: > According to Pádraig Brady on 9/10/2009 6:29 AM: >> While this patch is more verbose than my previous patch >> in this thread, it is more accurate. So let's drop the >> previous one. > >> + printf (_("\n\ >> +If none of the environment variables BLOCKSIZE, BLOCK_SIZE or >>

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Jim Meyering
Pádraig Brady wrote: > While this patch is more verbose than my previous patch > in this thread, it is more accurate. So let's drop the > previous one. However... > > The info was inaccurate for ls, so I've split the SIZE > specific info into a new emit_size_note(). That also > allows refactoring t

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Pádraig Brady
Eric Blake wrote: > According to Pádraig Brady on 9/10/2009 6:29 AM: >> While this patch is more verbose than my previous patch >> in this thread, it is more accurate. So let's drop the >> previous one. > >> + printf (_("\n\ >> +If none of the environment variables BLOCKSIZE, BLOCK_SIZE or >

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Pádraig Brady on 9/10/2009 6:29 AM: > While this patch is more verbose than my previous patch > in this thread, it is more accurate. So let's drop the > previous one. > + printf (_("\n\ > +If none of the environment variables BLOCKSI

Re: [PATCH] dd conv=unblock: print final newline consistently

2009-09-10 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 9/10/2009 6:24 AM: > > Currently, we're at gnulib (v0.0-2549-g2c90f1a) for the submodule. > None of the patches since then seemed to be essential to coreutils > on non-mingw/cygwin systems. Let me know if you'd like to us

Re: [PATCH] doc: du - clarify default blocksize in usage/manpage

2009-09-10 Thread Pádraig Brady
While this patch is more verbose than my previous patch in this thread, it is more accurate. So let's drop the previous one. However... The info was inaccurate for ls, so I've split the SIZE specific info into a new emit_size_note(). That also allows refactoring to be done in split and truncate.

Re: [PATCH] dd conv=unblock: print final newline consistently

2009-09-10 Thread Jim Meyering
Eric Blake wrote: > According to Jim Meyering on 9/10/2009 4:26 AM: >> I don't like last-minute changes, but this seems safe, considering it's in >> an obscure corner of dd. Who actually uses dd's conv=unblock option? >> Of those precious few, who would notice the additional newline that >> dd-wit

Re: [PATCH] dd conv=unblock: print final newline consistently

2009-09-10 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 9/10/2009 4:26 AM: > I don't like last-minute changes, but this seems safe, considering it's in > an obscure corner of dd. Who actually uses dd's conv=unblock option? > Of those precious few, who would notice the additiona

[PATCH] dd conv=unblock: print final newline consistently

2009-09-10 Thread Jim Meyering
I don't like last-minute changes, but this seems safe, considering it's in an obscure corner of dd. Who actually uses dd's conv=unblock option? Of those precious few, who would notice the additional newline that dd-with-this-patch now prints for most combinations of output size and conversion bloc