From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
Jiri Kosina <jkosina@suse.cz>
Subject: Re: [RFC v5]Update broken web addresses in arch directory.
Date: Thu, 14 Oct 2010 21:57:54 -0700 [thread overview]
Message-ID: <4CB7DF52.7060403@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.00.1010151524290.426@localhost>
On 10/14/2010 09:26 PM, Finn Thain wrote:
>
> On Thu, 14 Oct 2010, Justin P. Mattock wrote:
>
>> On 10/14/2010 07:38 PM, Finn Thain wrote:
>>>
>>> On Thu, 14 Oct 2010, Justin P. Mattock wrote:
>>>
>>>> hey jiri, whats the status of this? do you want to take this?
>>>> if so should I rebase the two patches to the current?
>>>
>>> The other patch needs to be resubmitted. Please see:
>>>
>>> http://groups.google.com.au/group/linux.kernel/msg/ce349d502567ebc4
>>>
>>> Finn
>>>
>>
>> ahh.. good catch... I'll resubmit that, but before I do is there any more?
>
> Why do you ask? Perhaps your email is broken and you are concerned that
> you did not receive some response that was already sent?
>
> Finn
>
well the web client is broken over here due to .gtkrc making it vary
laggy, so missing something might have happened over here..
as for asking, seems reasonable since theirs lots of traffic here and
there, and things fall through the cracks..(but could be wrong).
Justin P. Mattock
next prev parent reply other threads:[~2010-10-15 4:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 20:48 [RFC v5]Update broken web addresses in arch directory Justin P. Mattock
2010-10-05 0:55 ` Finn Thain
2010-10-15 1:24 ` Justin P. Mattock
2010-10-15 2:38 ` Finn Thain
2010-10-15 3:01 ` Justin P. Mattock
2010-10-15 4:26 ` Finn Thain
2010-10-15 4:57 ` Justin P. Mattock [this message]
2010-10-15 9:13 ` Jiri Kosina
2010-10-15 9:49 ` Justin P. Mattock
2010-10-15 18:59 ` Justin P. Mattock
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=4CB7DF52.7060403@gmail.com \
--to=justinmattock@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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