public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Stephen John Smoogen <smooge@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: Cygwin 2.6.0-1
Date: Wed, 31 Aug 2016 18:32:00 -0000	[thread overview]
Message-ID: <CANnLRdjzXgM7=iWeh475C2=XYU+mMYRmfw2qD_yKFg0ocetP5A@mail.gmail.com> (raw)
In-Reply-To: <80741012-9665-fe84-67b2-02d0ec6b3e76@frontier.com>

On 31 August 2016 at 12:28, Nirgendsdorf <nirgendsdorf@frontier.com> wrote:
> On Wed, 31 Aug 2016 15:58:45 +0200, Corinna Vinschen wrote:
>
>> I uploaded a new Cygwin release 2.6.0-1.
>>
>> Please note that this release won't work on Windows XP and Windows
>> Server 2003 or 2003 R2.  At least Windows Vista or Windows Server 2008
>> are required.
>
>
> Well, there goes XP as another software project on which I depend withdraws
> support. It’s not that I can’t afford to "upgrade"-- I can get a
> reconditioned box with Windows 7 on it for around $200 or less. It's that I
> am too old and tired to install the applications and utilities I would want,
> find replacements for my old favorites that would not run on the new box,
> and then tweak everything the way I would want it to run. Worse yet, I would
> probably want to install Linux...and build it from scratch. Nope, far too
> old and tired for any of that, especially for learning my way around the new
> stuff.
>

As the 84 year old guy who helps my 70 year old dad do Linux installs
and Cygwin fixes on systems keeps telling me: you are never too old...
it just takes a bit longer to get the circuits going.


>> Thanks,
>> Corinna
>
> Thank you, Corinna, for helping to keep Cygwin going. I found it when it was
> ver. b17 because I was looking for a way to run Joseph Allen's editor (joe)
> on Windows and keep all the nice POSIX features. It's been quite a ride ever
> since. I'll probably be around for a little while yet, long as I can build
> stuff for the old Cygwin without too much trouble. Goodness help me, though,
> if I ever get to the point where I find myself sitting in a wheelchair,
> staring at a wall.
>
> Cheers,
>
> Jeff
>
>
> --
> 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
>



-- 
Stephen J Smoogen.

--
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-08-31 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 14:46 Corinna Vinschen
2016-08-31 18:22 ` Nirgendsdorf
2016-08-31 18:32   ` Stephen John Smoogen [this message]
     [not found]     ` <58CFAA05-3193-4301-95A0-D611DA276079@solidrocksystems.com>
2016-08-31 19:12       ` Vince Rice
2016-08-31 19:17         ` Kenneth Wolcott
2016-08-31 19:30           ` Brian Inglis
2016-08-31 20:17             ` Marco Atzeri
2016-08-31 20:27             ` Achim Gratz
2016-10-02 11:01 ` Thomas Wolff
2016-10-19 11:38   ` Corinna Vinschen

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='CANnLRdjzXgM7=iWeh475C2=XYU+mMYRmfw2qD_yKFg0ocetP5A@mail.gmail.com' \
    --to=smooge@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).