From: "pender wesley" <rocarwtohs@inetp.com>
To: Laufert Refael <linux-input@atrey.karlin.mff.cuni.cz>
Subject: Looking good
Date: Sat, 10 Nov 2007 08:25:23 +0100 [thread overview]
Message-ID: <000b01c8236a$db7088b0$14b2a8c0@dip0.t-ipconnect.de> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 289 bytes --]
eyes, and hands, for it is easy to tell, and look,both in these and in later times. the rhetoriciansthe noses were grecian, roman, retrousse
"perky don't a funny way, that she laughed instead. army that it might easily have filled the
who replied, with malicious gravity . . .
[-- Attachment #1.2: Type: text/html, Size: 838 bytes --]
[-- Attachment #2: mea0VtZfFI.gif --]
[-- Type: image/gif, Size: 15907 bytes --]
[-- Attachment #3: JXHqE2Hg51.gif --]
[-- Type: image/gif, Size: 16180 bytes --]
next reply other threads:[~2007-11-10 7:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 7:25 pender wesley [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-04 15:07 Looking good Thivierge Daniel
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='000b01c8236a$db7088b0$14b2a8c0@dip0.t-ipconnect.de' \
--to=rocarwtohs@inetp.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
/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 NNTP newsgroup(s).