public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <Adam.Dinwoodie@metaswitch.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Please test snapshots
Date: Fri, 17 Aug 2012 17:46:00 -0000	[thread overview]
Message-ID: <CE9C056E12502146A72FD81290379E9A496019FE@ENFIRHMBX1.datcon.co.uk> (raw)
In-Reply-To: <20120817142506.GB20284@ednor.casa.cgf.cx>

Christopher Faylor wrote
> On Fri, Aug 17, 2012 at 09:07:30AM +0000, Adam Dinwoodie wrote:
>> I'm still seeing exactly the same issue having taken the 20120816 snapshot.
>> If anything, I've been hitting the problem more.
>
> I should have asked this before:  I don't think anyone has made it clear if
> they are running the cygwin ping or the Windows one.  I've been assuming
> Cygwin.  Is that correct?

Yes, Cygwin ping. For paranoia's sake, you can check the output I pasted in my
previous email, which should look like Cygwin ping rather than Windows ping
output. Also:

    $ cygcheck -c ping
    Cygwin Package Information
    Package              Version        Status
    ping                 1.0-1          OK

    $ cygcheck -f $(which ping)
    ping-1.0-1

    $ which ping
    /usr/bin/ping

    $ cygcheck ping
    Found: C:\cygwin\bin\ping.exe
    Found: C:\Windows\system32\ping.exe
    C:\cygwin\bin\ping.exe
      C:\cygwin\bin\cygwin1.dll
        C:\Windows\system32\KERNEL32.dll
          C:\Windows\system32\API-MS-Win-Core-RtlSupport-L1-1-0.dll
          C:\Windows\system32\ntdll.dll
            ...blah blah blah...

--
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

  reply	other threads:[~2012-08-17 15:52 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  3:53 Christopher Faylor
2012-08-06  5:14 ` Daniel Colascione
2012-08-06  8:59 ` Achim Gratz
2012-08-08 13:04   ` Achim Gratz
2012-08-09  8:07     ` Achim Gratz
2012-08-06 15:31 ` Filipp Gunbin
2012-08-06 23:27   ` Daniel Colascione
2012-08-07  0:39     ` Daniel Colascione
2012-08-07  0:40       ` Daniel Colascione
2012-08-08 22:17       ` Christopher Faylor
2012-08-09  6:35         ` Daniel Colascione
2012-08-09 12:29         ` Achim Gratz
2012-08-09 14:54           ` Christopher Faylor
2012-08-09 15:06             ` Achim Gratz
2012-08-09 14:59           ` Daniel Colascione
2012-08-10  7:15             ` Achim Gratz
2012-08-10 14:36               ` Christopher Faylor
2012-08-10 18:12                 ` Achim Gratz
2012-08-10 18:34                   ` Christopher Faylor
2012-08-10 19:08                     ` Achim Gratz
2012-08-10 20:24                       ` Christopher Faylor
2012-08-10 20:37                         ` Achim Gratz
2012-08-10 23:31                           ` Christopher Faylor
2012-08-14 13:45                 ` Adam Dinwoodie
2012-08-16 19:01                   ` Christopher Faylor
2012-08-16 19:33                     ` Ken Brown
2012-08-16 19:45                       ` Christopher Faylor
2012-08-16 20:11                         ` Ken Brown
2012-08-17  9:38                     ` Adam Dinwoodie
2012-08-17 14:37                       ` Christopher Faylor
2012-08-17 17:46                         ` Adam Dinwoodie [this message]
2012-08-17 18:08                           ` Christopher Faylor
2012-08-17 19:32                         ` Achim Gratz
2012-08-17  9:40           ` Achim Gratz
2012-08-17 10:47             ` Achim Gratz
2012-08-14 19:23 ` jojelino
2012-08-14 19:41   ` Corinna Vinschen
2012-08-14 19:42     ` Christopher Faylor

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=CE9C056E12502146A72FD81290379E9A496019FE@ENFIRHMBX1.datcon.co.uk \
    --to=adam.dinwoodie@metaswitch.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).