From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: trivial@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-usb@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-fbdev@vger.kernel.org,
alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org,
linux-ide@vger.kernel.org
Subject: Re: [RFC 2/3 v3]update web addresses in stagging
Date: Fri, 24 Sep 2010 17:51:56 -0700 [thread overview]
Message-ID: <4C9D47AC.6000002@gmail.com> (raw)
In-Reply-To: <20100925003406.GA30029@kroah.com>
On 09/24/2010 05:34 PM, Greg KH wrote:
> On Fri, Sep 24, 2010 at 05:08:56PM -0700, Justin P. Mattock wrote:
>> The below patch, is a simple fix to a broken web address not using a period in it's
>> name. I'll leave this up to you guys if you want to use it...
>>
>> Signed-off-by: Justin P. Mattock<justinmattock@gmail.com>
>
> I'll queue it up, thanks.
>
> Oh, it's "staging", not "stagging" as you have up there in the Subject:
> :)
>
> thanks,
>
> greg k-h
>
shoot... and I actually changed it from staging to stagging thinking
that was correct..(duh)..
Anyways alright.. I'll exclude this one if the other sets get finalized.
Justin P. Mattock
next prev parent reply other threads:[~2010-09-25 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 0:08 [RFC 1/3 v3]update web addresses in the kernel Justin P. Mattock
[not found] ` <1285373337-10945-1-git-send-email-justinmattock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-09-25 0:08 ` [RFC 2/3 v3]update web addresses in stagging Justin P. Mattock
2010-09-25 0:34 ` Greg KH
2010-09-25 0:51 ` Justin P. Mattock [this message]
[not found] ` <4C9D47AC.6000002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-09-25 20:47 ` Matthew Dharm
2010-09-25 21:30 ` Justin P. Mattock
2010-09-25 0:08 ` [RFC 3/3 v3]update broken web addresses archive dot org Justin P. Mattock
2010-09-26 9:43 ` [RFC 1/3 v3]update web addresses in the kernel Finn Thain
2010-09-26 13:42 ` 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=4C9D47AC.6000002@gmail.com \
--to=justinmattock@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).