-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to RE on 2/2/2005 3:11 AM: > Hi Eric, > > Maybe you can answer my question or help me with my "sparse problem" which I > am quoting in the following once again. [BTW I don't know if the patch you > sent me will be needed, but if yes, I would not know how to apply it ;-((( ]
You never stated which platform you are using; the output of `cp - --version' and `uname -a' would be useful in your bug report. Are you using cygwin or mingw, or are you accessing the NTFS drive remotely from a *nix box? If your problem is with the cygwin port of cp, then the cygwin AT cygwin DOT com mailing list is the correct place to ask; I see you've repeated your question there, so I will let that thread answer your question. The patch I sent was for the coreutils test suite, and has no bearing on the actual cp command. - -- Life is short - so eat dessert first! Eric Blake [EMAIL PROTECTED] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCANNv84KuGfSFAYARAr6KAJ44haWj8ZHnfPNblc6vN/mgHBy59gCeMczA s6HhkIBfpgMOM8/EqN9Dtzk= =Q9sc -----END PGP SIGNATURE----- _______________________________________________ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils