From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Updated [test]: coreutils-8.24-2
Date: Wed, 26 Aug 2015 23:28:00 -0000 [thread overview]
Message-ID: <55DE4006.7090306@redhat.com> (raw)
In-Reply-To: <001c01d0e04c$d8ebc210$8ac34630$@bonhard.uklinux.net>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
On 08/26/2015 04:16 PM, Fergus wrote:
> Yesterday's update from coreutils-8.23-4 to 8.24-1 has done something
> horrible to cp. Previously
> cp -r {sourcepath}/subdirectory {targetpath}
> is allowed even when {targetpath}/subdirectory already exists - which, very
> often or even usually, it does.
> Surely this is an accident and not an intended property of the update??
Not documented in NEWS, so it is an accident. I'm investigating now. It
does not reproduce on Linux, so it appears to be a bug in my
Cygwin-specific patches; in particular, I had problems where the file
src/cp.c changed upstream between 8.23 and 8.24, and where I may have
misported part of the cygwin-specific patches to that file when carrying
them forward between versions.
> I have not tried [test]: coreutils-8.24-2 and I do not know whether this and
> maybe other peculiarities of 8.24-1
> have been identified and corrected, but hope that this will eventually
> happen?
No, you're the first to report it (so 8.24-2 has the same issue), but
now that I know about it, it will get fixed soon.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-08-26 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:50 Fergus
2015-08-26 23:28 ` Fergus
2015-08-26 23:50 ` Eric Blake
2015-08-27 20:26 ` Sam Edge
2015-08-27 20:51 ` Peter Rosin
2015-08-27 21:40 ` Helmut Karlowski
2015-08-28 0:53 ` Sam Edge
2015-08-26 23:28 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55DE4006.7090306@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).