From: jwang <jwang25610@gmail.com>
To: cygwin@cygwin.com
Subject: Re: rsync failed after windows 10 update
Date: Tue, 05 Mar 2019 15:25:00 -0000 [thread overview]
Message-ID: <1551799218901-0.post@n5.nabble.com> (raw)
In-Reply-To: <1551791446810-0.post@n5.nabble.com>
Not sure if this (update to the latest Cygwin snapshots) will fix my issue
though as all my other "Windows 10" boxes, all have the great Cygwin
installed, have no such an issue.
Is it possible that some Windows back-end services stopped ?
Thanks a lot in advance
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
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:[~2019-03-05 15:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 12:19 jwang
2019-03-04 12:36 ` Corinna Vinschen
2019-03-04 14:44 ` jwang
2019-03-05 9:46 ` jwang
2019-03-05 12:04 ` Corinna Vinschen
2019-03-05 13:16 ` jwang
2019-03-05 15:25 ` jwang [this message]
2019-03-06 10:00 ` jwang
2019-03-06 11:57 ` Corinna Vinschen
2019-03-06 12:05 ` jwang
2019-03-06 12:14 ` Corinna Vinschen
2019-03-06 14:00 ` jwang
2019-03-08 13:59 ` jwang
2019-03-08 14:18 ` Houder
2019-03-08 15:35 ` jwang
2019-03-08 20:59 ` Jerry Baker via cygwin
2019-03-09 1:23 ` jwang
2019-03-09 9:16 ` jwang
2019-03-11 15:02 ` jwang
2019-03-12 10:29 ` jwang
2019-03-16 8:36 ` jwang
2019-03-16 10:30 ` Houder
2019-03-16 10:49 ` jwang
2019-03-16 12:45 ` Houder
2019-03-16 13:13 ` jwang
2019-03-16 13:19 ` jwang
2019-03-16 13:26 ` jwang
2019-03-16 13:46 ` Houder
2019-03-16 14:18 ` jwang
2019-03-16 13:31 ` Houder
2019-03-17 6:45 ` Achim Gratz
2019-03-17 8:15 ` jwang
2019-03-17 9:07 ` Eliot Moss
2019-03-18 9:47 ` jwang
2019-04-02 8:45 ` jwang
2019-03-05 12:20 ` Andrey Repin
2019-03-05 13:15 ` jwang
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=1551799218901-0.post@n5.nabble.com \
--to=jwang25610@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).