From: Eric Blake <ebb9@byu.net>
To: cygwin-talk@cygwin.com
Subject: Re: once more unto the breech - please try a snapshot so I can release this thing
Date: Wed, 11 Jan 2006 14:13:00 -0000 [thread overview]
Message-ID: <43C5126E.8080600@byu.net> (raw)
In-Reply-To: <20060111022341.GA31671@trixie.casa.cgf.cx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I hope you meant breach[1], not breech[2]. Otherwise, I'd have to send a
hippo after you (think of the children!). Your subject reminded me of one
of the early English translations of the Bible, where the translator
picked the wrong word in Genesis 3:7 (http://sunnyokanagan.com/breeches/).
Oh, and I finally subscribed to the cygwin-talk list; I've had far too
many laughs reading the web archives for me to lurk any longer.
>
> Failure to provide any of the above in a report will result in taunting
> and/or mocking. You have been warned.
So bring on the taunting - I didn't provide any cygcheck details!
>
> Oh. And, fixes are always welcome.
Fixes? On an open source project? Who would have thought it possible?
[1]http://dictionary.reference.com/search?q=breach
[2]http://dictionary.reference.com/search?q=breech
- --
Life is short - so eat dessert first!
Eric Blake ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDxRJu84KuGfSFAYARAn/RAJ9btkvfoNz2VA44jTIs8TZCkUwoYgCgoOWm
N2/0ZJi151svpzyvcvvJg6Q=
=5h1u
-----END PGP SIGNATURE-----
next parent reply other threads:[~2006-01-11 14:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060111022341.GA31671@trixie.casa.cgf.cx>
2006-01-11 14:13 ` Eric Blake [this message]
2006-01-11 14:33 Williams, Gerald S (Jerry)
2006-01-11 16:05 ` Christopher Faylor
2006-01-11 17:33 ` Dave Korn
2006-01-11 22:02 ` One Angry User
2006-01-12 0:08 ` Igor Peshansky
2006-01-12 0:18 ` Igor Peshansky
2006-01-12 10:51 ` Dave Korn
2006-01-12 13:32 ` Igor Peshansky
2006-01-12 21:34 ` Joe Smith
2006-01-12 22:01 ` Ed C. Lueless
2006-01-13 0:07 ` Igor Peshansky
2006-01-13 15:01 ` Joe Smith
2006-01-13 15:10 ` Dave Korn
2006-01-13 15:11 ` Corinna Vinschen
2006-01-13 16:38 ` Igor Peshansky
2006-01-13 16:49 ` Eric Blake
2006-01-13 16:59 ` Igor Peshansky
2006-01-13 17:06 ` Ed C. Lueless
2006-01-13 17:15 ` Dave Korn
2006-01-13 16:54 ` Dave Korn
2006-01-13 17:00 ` Igor Peshansky
2006-01-13 17:08 ` Dave Korn
2006-01-13 17:15 ` Dave Korn
2006-01-13 17:42 ` Igor Peshansky
2006-01-13 17:59 ` Dave Korn
2006-01-12 4:30 ` Gary R. Van Sickle
2006-01-15 5:20 ` * *
2006-01-15 5:41 ` Gary R. Van Sickle
2006-01-16 10:33 ` Dave Korn
2006-01-17 15:26 Williams, Gerald S (Jerry)
2006-01-17 15:38 ` Dave Korn
2006-01-18 18:13 Williams, Gerald S (Jerry)
2006-01-18 18:27 ` Dave Korn
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=43C5126E.8080600@byu.net \
--to=ebb9@byu.net \
--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).