From: "Brent Watson" <brent.watson-0T2qRkA73kE6cRZTx1dUA3S5uNuOjpZe@public.gmane.org>
To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Southern California Linux Expo - SCALE Attendee List
Date: Mon, 19 Feb 2018 22:52:22 +0530 [thread overview]
Message-ID: <033e01d3a9a6$37480b50$a5d821f0$@tradeshowattendees.com> (raw)
In-Reply-To:
Greetings,
Would you be interested in Southern California Linux Expo - SCALE ?
We can provide you with 3,600 attendee contacts with their complete details
(First Name, Middle Name, Last Name, Company, Web site/URL, Contact number,
Fax number, Email Id, Industry, Employee size, Revenue size, Country, state,
Zip Code and LinkedIn URL.)
Please keep me posted if you are interested and I shall get back to you with
Pricing and more details.
I Look forward to hearing from you.
Warm regards,
Brent Watson
Demand Generation Executive
If you don't wish to receive our newsletters, reply back with "unsubscribe "
in subject line
reply other threads:[~2018-02-19 17:22 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='033e01d3a9a6$37480b50$a5d821f0$@tradeshowattendees.com' \
--to=brent.watson-0t2qrka73ke6crztx1dua3s5unuojpze@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
/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).