linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Greg KH <greg@kroah.com>,
	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: Sat, 25 Sep 2010 14:30:49 -0700	[thread overview]
Message-ID: <4C9E6A09.10007@gmail.com> (raw)
In-Reply-To: <20100925204736.GD25677@one-eyed-alien.net>

On 09/25/2010 01:47 PM, Matthew Dharm wrote:
> On Fri, Sep 24, 2010 at 05:51:56PM -0700, Justin P. Mattock wrote:
>> 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.
>
> One random suggestion:  Perhaps you should include a date here?  i.e. "URL
> blah blah blah (as of Sept 2010)"
>
> That way, people have some idea how much they can trust that URL without
> having to dig into the kernel history to see when it was last changed.
>
> Matt
>


well.. as it stand right now doing grep -Re "http" in all the 
directories(minus COPYING/MAINTAINERS) gave me a little over 2000
addresses to check(not so bad, only a few days worth of checking(finding 
the broken address is time consuming)).. so I could go back and do this 
for all of them except the webarchive addresses that are broken(maybe 
put a tag on them saying use_webarchive or something).
then there is the question of how much more bloated will the kernel get 
with such a thing(I'm guessing not much, but then again you never know).

Justin P. Mattock

  reply	other threads:[~2010-09-25 21:30 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
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
2010-09-25 20:47       ` Matthew Dharm
2010-09-25 21:30         ` Justin P. Mattock [this message]
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=4C9E6A09.10007@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).