From: Pete Kelly <ramsfanxxxiv@yahoo.com>
To: "cathyk35@comcast.net" <cathyk35@comcast.net>,
"ckristoff1@msn.com" <ckristoff1@msn.com>,
"luckybob4@juno.com" <luckybob4@juno.com>,
"janel450@yahoo.com" <janel450@yahoo.com>,
"java@gcc.gnu.org" <java@gcc.gnu.org>,
"marie@thegarretgroup.com" <marie@thegarretgroup.com>,
"mmmk6161@aol.com" <mmmk6161@aol.com>,
"lindameiercpa@sbcglobal.net" <lindameiercpa@sbcglobal.net>,
"mike.mccarthy@opco.com" <mike.mccarthy@opco.com>,
"mkelly210@aol.com" <mkelly210@aol.com>
Subject: brigitte guegan
Date: Sat, 13 Mar 2010 04:01:00 -0000 [thread overview]
Message-ID: <636507.31383.qm@web36706.mail.mud.yahoo.com> (raw)
http://radiuslogistics.net/virginie.html
reply other threads:[~2010-03-13 4:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=636507.31383.qm@web36706.mail.mud.yahoo.com \
--to=ramsfanxxxiv@yahoo.com \
--cc=cathyk35@comcast.net \
--cc=ckristoff1@msn.com \
--cc=janel450@yahoo.com \
--cc=java@gcc.gnu.org \
--cc=lindameiercpa@sbcglobal.net \
--cc=luckybob4@juno.com \
--cc=marie@thegarretgroup.com \
--cc=mike.mccarthy@opco.com \
--cc=mkelly210@aol.com \
--cc=mmmk6161@aol.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).