From: Wladimir Mutel <mwg@mwg.dp.ua>
To: cygwin@cygwin.com
Subject: Re: Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32
Date: Tue, 30 Sep 2014 11:49:00 -0000 [thread overview]
Message-ID: <20140930113903.GA14099@c540scadaw> (raw)
In-Reply-To: <542A4F29.80204@mwg.dp.ua>
Dear all, please disregard this thread.
It was a false alarm because I did not have unzip installed under Cygwin64
and its shell found some stray unzip from Dell utilities in Windows path.
Sorry for disturbing you without grounds.
On Tue, Sep 30, 2014 at 09:35:21AM +0300, Wladimir Mutel wrote:
> Dear all,
--
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:[~2014-09-30 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:32 Wladimir Mutel
2014-09-30 9:06 ` Marco Atzeri
2014-09-30 11:49 ` Wladimir Mutel [this message]
[not found] <542A6B85.5030700@mwg.dp.ua>
2014-09-30 11:39 ` Marco Atzeri
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=20140930113903.GA14099@c540scadaw \
--to=mwg@mwg.dp.ua \
--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).