From: Andy Koppe <andy.koppe@gmail.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: Moving Cygwin directory safe?
Date: Sun, 27 Jun 2010 19:53:00 -0000 [thread overview]
Message-ID: <AANLkTim1WbXcAKfhMvYoehHuSboN_Ur8eKcoSymvmrHX@mail.gmail.com> (raw)
In-Reply-To: <87eifs9rwz.fsf@gmail.com>
Paul Bibbings wrote:
> Christopher Faylor writes:
>> I appreciate that you've moved to cygwin-talk but this does not qualify
>> as something which is even remotely related to Cygwin in any way. Please
>> don't discuss sports here.
>
> You set the rules. Football, not OK.
Hippo polo should be fine though.
Andy
next prev parent reply other threads:[~2010-06-27 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100626141016.GD3672@wladimir>
[not found] ` <3710255202.20100627051050@mtu-net.ru>
[not found] ` <20100627095521.GI3672@wladimir>
[not found] ` <20100627133726.GA5344@wladimir>
[not found] ` <4C27826E.8020909@monai.ca>
[not found] ` <20100627173112.GB5344@wladimir>
2010-06-27 18:58 ` Paul Bibbings
2010-06-27 19:06 ` Christopher Faylor
2010-06-27 19:50 ` Paul Bibbings
2010-06-27 19:53 ` Andy Koppe [this message]
2010-06-28 13:34 ` Warren Young
2010-06-28 3:34 ` 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=AANLkTim1WbXcAKfhMvYoehHuSboN_Ur8eKcoSymvmrHX@mail.gmail.com \
--to=andy.koppe@gmail.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).