From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: hooray hippos at last <cygwin-talk@cygwin.com>
Subject: Re: ls sources
Date: Thu, 11 Mar 2010 13:19:00 -0000 [thread overview]
Message-ID: <4B98F212.6010400@gmail.com> (raw)
In-Reply-To: <20100311131655.GI6505@calimero.vinschen.de>
On 11/03/2010 13:16, Corinna Vinschen wrote:
> They are of course secret. We're using the famous cryptographic encoding
> called "C++". Only hippos really have a chance to break it.
Hippos can break anything! Assuming they fall from a sufficient height!
cheers,
DaveK
next prev parent reply other threads:[~2010-03-11 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 11:23 Vincent Richomme
2010-03-11 12:13 ` Vincent Richomme
2010-03-11 13:02 ` Andy Koppe
2010-03-11 13:11 ` Vincent Richomme
2010-03-11 13:17 ` Dave Korn
2010-03-11 13:25 ` Vincent Richomme
2010-03-11 13:29 ` Mike Marchywka
2010-03-11 13:17 ` Corinna Vinschen
2010-03-11 13:19 ` Dave Korn [this message]
2010-03-11 14:51 ` Eric Blake
2010-03-11 15:04 ` Andy Koppe
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=4B98F212.6010400@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).