From: Kenneth Wolcott <kennethwolcott@gmail.com>
To: cygwin@cygwin.com
Subject: Cygwin mv and cp fail: skipping file 'file', as it was replaced while being copied
Date: Tue, 12 Apr 2016 18:13:00 -0000 [thread overview]
Message-ID: <CADex0xxjBV0mwARirriUt9oSfBdSucsQRRXVsxfyH6_x1jf+DQ@mail.gmail.com> (raw)
Hi;
Cygwin mv and cp fail: skipping file 'file', as it was replaced
while being copied
$ uname -a
CYGWIN_NT-6.1 KWOLCOTT-9010 2.5.0(0.297/5/3) 2016-04-11 09:58 x86_64 Cygwin
$ mv new_Perforce_account_request.txt ~/.
mv: skipping file 'new_Perforce_account_request.txt', as it was
replaced while being copied
$ pwd
/cygdrive/p/Engineering/EOSS_Tableau/SFDC
$ cp new_Perforce_account_request.txt ~/.
cp: skipping file 'new_Perforce_account_request.txt', as it was
replaced while being copied
What's up with this?
Thanks,
Ken Wolcott
--
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 reply other threads:[~2016-04-12 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 18:13 Kenneth Wolcott [this message]
2016-04-12 18:54 ` Eric Blake
2016-04-12 19:01 ` Kenneth Wolcott
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=CADex0xxjBV0mwARirriUt9oSfBdSucsQRRXVsxfyH6_x1jf+DQ@mail.gmail.com \
--to=kennethwolcott@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).