From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Fun with cp -R error when both foo and foo.exe exist
Date: Tue, 09 Oct 2018 06:22:00 -0000 [thread overview]
Message-ID: <f00936b7-cc2a-1a2c-7862-c79e10bed95d@gmail.com> (raw)
In-Reply-To: <CAPF-yObTngOGu_+TSfSQo4bpi_tJ3572r_26cfidLZ5QpcPGYQ@mail.gmail.com>
Am 08.10.2018 um 23:24 schrieb Dan Kegel:
>
> A nice workaround might be for the cygwin version of cp could arrange
> to wait to create .exe files until after any potential non-suffixed
> file has been processed... not sure how easy that would be.
>
> Apologies if this has already been discussed.
> - Dan
it is not cp handling the magic, but the cygwin dll.
Regards
Marco
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-10-09 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 21:25 Dan Kegel
2018-10-09 6:22 ` Marco Atzeri [this message]
2018-10-09 12:03 ` Eric Blake
2018-10-09 16:22 ` Dan Kegel
2018-10-09 16:52 ` Eric Blake
2018-10-09 17:19 ` Dan Kegel
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=f00936b7-cc2a-1a2c-7862-c79e10bed95d@gmail.com \
--to=marco.atzeri@gmail.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).