From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin-talk@cygwin.com
Subject: Re: Dinner for One. Was: Re: [ITP] perl-XML-Simple
Date: Wed, 26 Aug 2009 05:08:00 -0000 [thread overview]
Message-ID: <416096c60908252208t7dcb1203meedd99b0fb6f7cd@mail.gmail.com> (raw)
In-Reply-To: <4A949317.4060505@veritech.com>
Lee D. Rothstein:
> Corinna Vinschen wrote:
>>
>> Same procedure as every year, James(*).
>>
>>
>> Corinna
>>
>> (*) http://en.wikipedia.org/wiki/Dinner_for_One
>>
>>
>
> Nice easter egg!, Corinna.
More of a New Year's Eve punch really.
;) Andy
prev parent reply other threads:[~2009-08-26 5:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A8D9191.70207@users.sourceforge.net>
[not found] ` <4A919D6D.2030405@users.sourceforge.net>
[not found] ` <20090824112206.GA8907@calimero.vinschen.de>
[not found] ` <4A92BDB1.4080907@users.sourceforge.net>
[not found] ` <20090824202155.GA10456@calimero.vinschen.de>
2009-08-26 1:43 ` Lee D. Rothstein
2009-08-26 5:08 ` Andy Koppe [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=416096c60908252208t7dcb1203meedd99b0fb6f7cd@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).