From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
jkosina@suse.cz, "Maciej W. Rozycki" <macro@linux-mips.org>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH 1/2 v4]Update broken web addresses in arch directory.
Date: Fri, 01 Oct 2010 21:00:47 -0700 [thread overview]
Message-ID: <4CA6AE6F.9030708@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.00.1010021353250.289@localhost>
On 10/01/2010 08:55 PM, Finn Thain wrote:
>
> On Fri, 1 Oct 2010, Justin P. Mattock wrote:
>
>> On 10/01/2010 05:47 AM, Finn Thain wrote:
>>
>>
>> man what a pain.. I want this fuc*ing sh*t out of here..(tired of web
>> addresses)oh-well the learning process of development.. Ill resend with the
>> fixes.
>>
>
> I know what you mean. But I think it is true what they say: poor
> documentation is worse than none.
>
> Finn
>
I was just messn(didn't mean to curse..).. over here in SoCal were
having a heat wave so it's sticky and gross making things more challenging..
but yeah it is better than none.. but should be done properly..
Justin P. Mattock
prev parent reply other threads:[~2010-10-02 4:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 13:51 [PATCH 1/2 v4]Update broken web addresses in arch directory Justin P. Mattock
2010-09-30 13:51 ` [PATCH v5]update broken web addresses in the kernel Justin P. Mattock
2010-10-01 13:12 ` Finn Thain
2010-10-01 12:47 ` [PATCH 1/2 v4]Update broken web addresses in arch directory Finn Thain
2010-10-01 16:13 ` Justin P. Mattock
2010-10-02 3:55 ` Finn Thain
2010-10-02 4:00 ` Justin P. Mattock [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=4CA6AE6F.9030708@gmail.com \
--to=justinmattock@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=rdunlap@xenotime.net \
--cc=trivial@kernel.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 NNTP newsgroup(s).