public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Corrupt Cygwin64 install?
Date: Wed, 28 Sep 2016 00:06:00 -0000	[thread overview]
Message-ID: <74eb1aa0-2fc9-f1e6-4209-b67ce4add549@SystematicSw.ab.ca> (raw)
In-Reply-To: <CACt7iwkyJZk0XCqvV9D4b7-di_XcL2Bckn_9yBsgRgxyMJXMnw@mail.gmail.com>

On 2016-09-27 14:02, Mike McCarty wrote:
> Thanks, I dug around in the registry based on your info and those (or
> similar) entries are already there and the folder my cygwin install is
> in was already listed so either those registry entries are
> anachronisms or don't have the needed effect.

Please note that the OP on the other thread excluded the .../cygwin/bin
directory, not the parent install directory.

Bottom posting only on this list/group please?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2016-09-27 23:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 22:35 Mike McCarty
2016-09-22 14:18 ` Ken Brown
2016-09-26 21:09   ` Mike McCarty
2016-09-27  2:00     ` Ken Brown
2016-09-27  2:18       ` Brian Inglis
2016-09-27 15:05         ` Mike McCarty
2016-09-27 17:59     ` Achim Gratz
2016-09-27 18:06       ` Mike McCarty
2016-09-27 18:12         ` Achim Gratz
2016-09-27 18:29           ` Achim Gratz
2016-09-27 20:15             ` Mike McCarty
2016-09-28  0:06               ` Brian Inglis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-21 22:04 Mike McCarty
2016-09-21 22:09 ` Ken Brown

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=74eb1aa0-2fc9-f1e6-4209-b67ce4add549@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).