From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: The Vulgar and Apparently-Not-So-Famous-After-All Last Words
Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: Re: Installing 1.7 alongside 1.5 - can it be done safely?
Date: Wed, 30 Sep 2009 13:26:00 -0000 [thread overview]
Message-ID: <4AC35FDB.6070405@gmail.com> (raw)
In-Reply-To: <4AC17443.9060007@gmail.com>
Dave Korn wrote:
> David Antliff wrote:
>> On Tue, Sep 29, 2009 at 14:08, Chris Cormie <cjcormie@gmail.com> wrote:
>>> I followed this sage advice and so far my parallel 1.5 / 1.7 installs are
>>> not interfering with each other.
>> Thanks Chris, and DaveK. I shall proceed with caution :)
>
> " His story checks out. Let us proceed casually with our guards lowered.
> Forward and onward to complete safety! "
I guess I'm the only one round here who reads 8-bit theater?
http://www.nuklearpower.com/2009/08/08/episode-1160-game-face/
cheers,
DaveK
prev parent reply other threads:[~2009-09-30 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <db95995b0909281643udf9f125n902ae2c91c4136f@mail.gmail.com>
[not found] ` <4AC16C34.6050503@gmail.com>
[not found] ` <db95995b0909281911k57978759le43f4cc09e8c9fb0@mail.gmail.com>
2009-09-29 2:28 ` Dave Korn
2009-09-30 13:26 ` Dave Korn [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=4AC35FDB.6070405@gmail.com \
--to=dave.korn.cygwin@googlemail.com \
--cc=cygwin-talk@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).