From: "Peter Hardy" <norina.daughtee@starreklinte.inbox.as>
To: linux-input@atrey.karlin.mff.cuni.cz
Subject: To be or not to be. To be...
Date: Tue, 6 Nov 2007 17:36:04 +0800 [thread overview]
Message-ID: <01c8209b$815f1110$ee30e0dd@norina.daughtee> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: useit.gif --]
[-- Type: image/gif, Size: 7131 bytes --]
next reply other threads:[~2007-11-06 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 9:36 Peter Hardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-30 12:45 To be or not to be. To be Lynne Allen
2007-08-05 19:23 Isabel Rutherford
2007-08-03 10:04 Young Andrews
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='01c8209b$815f1110$ee30e0dd@norina.daughtee' \
--to=norina.daughtee@starreklinte.inbox.as \
--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).