Re: [PATCH] Fix preserve_mode when destination directory partially exists

On Fri, Jan 04, Paul Eggert wrote: Jan Blunck [EMAIL PROTECTED] writes: I found a bug with cp -p --parents when the destination partially exists and the filesystem isn't mounted with acls. $ mkdir -p a/b/c a/b/d e $ touch a/b/c/foo a/b/d/foo $ cp -p --parent a/b/c e $ cp -p

Re: [PATCH] Fix preserve_mode when destination directory partially exists

Jan Blunck [EMAIL PROTECTED] wrote: On Fri, Jan 04, Paul Eggert wrote: Jan Blunck [EMAIL PROTECTED] writes: I found a bug with cp -p --parents when the destination partially exists and the filesystem isn't mounted with acls. $ mkdir -p a/b/c a/b/d e $ touch a/b/c/foo a/b/d/foo

Re: fseeko failure [was: wcwidth failure on RedHat Linux 7.3 (coreutils-6.9.91)]

On Sun, Jan 06, 2008 at 06:26:16AM -0700, Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Peter Fales on 12/30/2007 11:46 PM: | This change fixes the problem in in test-wcwidth. There is one other | failure in test-fseeko.sh when building on RedHat 7.3. More

Re: tr '[:upper:]' '[:lower:]' -- misaligned construct

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jim Meyering wrote: Here's a tentative patch that also avoids repeated (and wasteful) initialization of the xlate array. I note that POSIX requires that, in the case that the arguments are exactly '[:lower:]' and '[:upper:]' (or the reverse of the

Re: tr '[:upper:]' '[:lower:]' -- misaligned construct

Micah Cowan [EMAIL PROTECTED] wrote: Jim Meyering wrote: Here's a tentative patch that also avoids repeated (and wasteful) initialization of the xlate array. I note that POSIX requires that, in the case that the arguments are exactly '[:lower:]' and '[:upper:]' (or the reverse of the same),

Re: printf failure on darwin with coreutils-6.9.91

Peter Fales [EMAIL PROTECTED] wrote: I'm trying to build coreutils-6.9.91 for Mac OS/X (Darwin 10.3) and getting test failures from misc/printf. The output of make check is attached below. I believe the problem occurs around line 345 of src/printf.c which has: 342 switch

Concern about --reply=no option of mv.

Folks, I noticed that the --reply option is being deprecated in mv. Perhaps I am overlooking something, but it appears as if key functionality is being removed from the command. I regularly write scripts with --reply=no with the intent that if the target file exists, the mv command fails.

Re: Concern about --reply=no option of mv.

On Mon, 7 Jan 2008, Dana Runge wrote: I noticed that the --reply option is being deprecated in mv. Perhaps I am overlooking something, but it appears as if key functionality is being removed from the command. I regularly write scripts with --reply=no with the intent that if the target file