Bruno Haible <[EMAIL PROTECTED]> wrote:
> On MacOS X 10.3.9, in a German locale, 3 tests fail because they compare a
> localized error message with an expected result in English. Here is a fix.
>
> 2006-12-28 Bruno Haible <[EMAIL PROTECTED]>
>
> * tests/chown/deref: Source lang-default.
>
Bruno Haible <[EMAIL PROTECTED]> wrote:
> 2006-12-26 Bruno Haible <[EMAIL PROTECTED]>
>
> * src/copy.c (copy_internal): Use mkfifo as a fallback if mknod fails.
> Needed on MacOS X.
Thanks. I applied this, too.
___
Bug-coreutils mailing
Evan Hunt <[EMAIL PROTECTED]> wrote:
>> > Very well. In that case, let's edit the documentation to reflect that .0
>> > represents the end of the field, and I'll be happy.
>>
>> I would welcome a patch (to coreutils.texi) to do that.
>
> Okay. First kick at the can is below; if you think it's too
Paul Eggert wrote:
Matthew Woehlke <[EMAIL PROTECTED]> writes:
sync() however /is/ missing from NSK and also (at least as my original
bug report indicated) Interix.
But coreutils should build on such systems. Its src/system.h has this:
#if ! HAVE_SYNC
# define sync() /* empty */
#en
Based on the comments I found trawling through the source, you guys
have seen this one coming. mv(1) tries calling rename(2) to begin
with, and if that fails and sets errno to EXDEV it falls back to a
copy/unlink strategy.
The issue of filesystems where rename(2) is not supported has arisen
- 9p o
Georg Schwarz <[EMAIL PROTECTED]> writes:
> What else could I try out?
What is the value of HAVE_WCTYPE_CTMP_BUG? It should be 1. For
example, what is the output of "diff -c lib/wctype_.h lib/wctype.h"?
If HAVE_WCTYPE_CTMP_BUG is wrong, we need to investigate why;
please look in config.log to
Just curious if there are any comments on how to improve this patch, or
is it just a bad idea to add this kind of functionality to a simple tool
like touch?
-Marc
Original Message
Subject:Re: Patch for touch to make it have a -p option, similar to
mkdir
Date: Thu,
Marc Abramowitz <[EMAIL PROTECTED]> wrote:
> Just curious if there are any comments on how to improve this patch, or
> is it just a bad idea to add this kind of functionality to a simple tool
> like touch?
Justification is what's lacking. "It's convenient" isnt' enough.
Adding a new option is a p