All of lore.kernel.org
 help / color / mirror / Atom feed
From: "gina@rfnow.com" <gina@rfnow.com>
To: unlisted-recipients:; (no To-header on input)
Subject: (No subject header)
Date: Tue, 26 Aug 2014 14:52:50 -0600	[thread overview]
Message-ID: <53fcf3a2.246.1dc8.8623@rfnow.com> (raw)



You have just won £1,000,000GBP.Please Contact your Claims
Personnel with your email only to. nellydave1@gmail.com .for
info
......................................................................
NOTE : If You Recieve This Message In Your
Junk Or Spam Its Due To Your Internet
Provider.

             reply	other threads:[~2014-08-26 21:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 20:52 gina [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-30 20:01 [PATCH 3/4] exec: unify compat_do_execve() code Oleg Nesterov
2010-12-01 17:37 ` (No subject header) Milton Miller
2010-12-01 17:37   ` Milton Miller
2010-12-01 18:27   ` Oleg Nesterov
2010-12-01 18:27     ` Oleg Nesterov
2010-11-09  7:27 Doubt about CRTSCTS preprocessor macro definition in termbits.h file Ramya Desai
2010-11-09 16:56 ` (No subject header) Milton Miller
2010-05-27  2:42 idle-test patches queued for upstream Len Brown
2010-05-27  2:42 ` [PATCH 1/8] cpuidle: fail to register if !CONFIG_CPU_IDLE Len Brown
2010-05-27  2:42   ` [PATCH 5/8] sched: clarify commment for TS_POLLING Len Brown
2010-05-27  5:25     ` (No subject header) Milton Miller
2010-05-27  5:25       ` Milton Miller
2010-05-27  5:47       ` Len Brown
2004-11-29 23:10 John Black
2004-11-29 23:00 John Black
2004-11-30  7:09 ` Brent Clark
2004-07-30  3:33 Jason Opperisano
2004-07-30  4:00 ` John Black
2004-07-28 16:01 John Black
2004-07-28 21:52 ` Antony Stone
2004-07-30  3:09   ` John Black

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=53fcf3a2.246.1dc8.8623@rfnow.com \
    --to=gina@rfnow.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.