From: thetruthbeforeus@firemail.cc
To: Tracy Smith <tlsmith3777@gmail.com>
Cc: thetruthstandsbeforeus@firemail.cc, debian-user@lists.debian.org,
linux-kernel@vger.kernel.org, rms@gnu.org,
linux-kernel-owner@vger.kernel.org
Subject: Re: The white man - Who he is. A Discussion - Fucking White Bitch
Date: Sun, 25 Feb 2018 16:32:31 +0000 [thread overview]
Message-ID: <2bf200477988a857441eea848ae55c98@firemail.cc> (raw)
In-Reply-To: <786F4FD5-F74E-4DCB-9945-FC0E940C6D54@gmail.com>
You got a problem with the truth, bitch?
On 2018-02-24 18:05, Tracy Smith wrote:
> Please block this junk email
>
> Sent from my iPhone
>
>> On Feb 24, 2018, at 9:49 AM, thetruthstandsbeforeus@firemail.cc wrote:
>>
>> Alot of folks have been wondering: why are things they way that they
>> are? Many have been pondering this notion. All things have roots: you,
>> me, we all do, but when we are cut from those roots we feel adrift in
>> this world. Like this world is not our own. In the past many of us
>> have been forcefully cut from those roots through no fault of our own
>> nor of our ancestors.
>>
>> To know why things are, you must know Who the people that do them,
>> are. What makes them do these things. Here's some straight truth from
>> someone who has been in the game for some time
>>
>> The white man -- Just Who, who really, he is (and why he do what he
>> does)
>>
>>
>> (Don't let th
>> ese words be silenced, those against the truth try to cast it into
>> darkness;
>> and with it - what with that which what makes us human)
>>
>>
>>
>> http://www.liveleak.com/view?i=76b_1519485315
>>
>>
>>
>>
>>
>> #blackpanther, #wealth, #power, #shaolin
prev parent reply other threads:[~2018-02-25 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 15:49 The white man - Who he is. A Discussion thetruthstandsbeforeus
2018-02-24 18:05 ` Tracy Smith
2018-02-25 16:32 ` thetruthbeforeus [this message]
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=2bf200477988a857441eea848ae55c98@firemail.cc \
--to=thetruthbeforeus@firemail.cc \
--cc=debian-user@lists.debian.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rms@gnu.org \
--cc=thetruthstandsbeforeus@firemail.cc \
--cc=tlsmith3777@gmail.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 NNTP newsgroup(s).