eady I don't know about?).
If anyone has some ideas I would be happy to produce a patch (assuming
you don't need copyright assignment).
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=9086
[2] https://lists.gnu.org/archive/html/coreutils/2018-06/msg00011.html
--
Mikael Magnusson
a lot of people, and neither the m4 file nor cp.c has
changed on those lines since xattr support was added... Disclaimer:
this is gentoo ;).
--
Mikael Magnusson
In my old 6.x something, cp would just say
cp: cannot copy a directory, `dir', into itself, `dir/dir'
(it would still do it, but only once)
In 7.1 I get a result like this:
% timeout 1 cp -rl dir dir
% ls -R dir|wc -l
1063
Without the -l it still behaves properly.
--
Mikael
ULL, 'o'},
{"random-source", required_argument, NULL, RANDOM_SOURCE_OPTION},
{"zero-terminated", no_argument, NULL, 'z'},
--
Mikael Magnusson
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
On Fri, 21 Oct 2005, Jim Meyering wrote:
Mikael Magnusson <[EMAIL PROTECTED]> wrote:
I have a file "a" and a fifo "b". Running "cp a b" prompts "cp: overwrite
b?", but answering yes just writes the contents of "a" into the fifo. If
on in --help or man cp).
This is even more confusing if you run something like cp /foo/* /bar and
you get "cp: overwrite arbitrary_file?" and you answer yes, it should then
be safe to assume all files from /foo are now in /bar if no error messages
pres
