public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Windows upgrade
Date: Thu, 14 Jun 2018 01:29:00 -0000	[thread overview]
Message-ID: <e675b2e0-aa00-612a-88c7-ac48b438dbea@t-online.de> (raw)
In-Reply-To: <CP2P152MB1793C5EA6179682AFEA781F8DC7F0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>

Am 13.06.2018 um 01:30 schrieb Alejandro Benitez:

> It's somehow clear I thankfully won't need to upgrade to cygwin64 until later, 

While you don't need to do it, you'll have to re-install Cygwin anyway, 
and frankly, installing 32-bit Cygwin from scratch, on a 64-bit Windows 
machine, just seems excessively nostalgic.

You're already removing so much cruft --- why let yourself be tied to 
the past by sticking with 32-bit Cygwin?

> I mean it seems I'll be able to still use my 32 bit cygwin after I upgrade to 64 bit Windows 10, 

Unlikely.  You'll have to do a complete re-install to fix up all the 
file permissions and regsitry entries.


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

      parent reply	other threads:[~2018-06-13 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  3:20 Alejandro Benitez
2018-06-13  6:12 ` Sam Habiel
2018-06-13 13:49   ` Andrey Repin
2018-06-13 14:39     ` Sam Habiel
2018-06-13  8:35 ` Andrey Repin
2018-06-13 18:37 ` Achim Gratz
2018-06-15 11:17   ` Andrey Repin
2018-06-14  1:29 ` Hans-Bernhard Bröker [this message]

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=e675b2e0-aa00-612a-88c7-ac48b438dbea@t-online.de \
    --to=hbbroeker@t-online.de \
    --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).