public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: FD Cami <francois.cami@free.fr>,
	Alex Howells <alex@bytemark.co.uk>, Nick Warne <nick@ukfsn.org>,
	trivial@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Documentation error: SubmittingPatches
Date: Fri, 10 Oct 2008 11:25:48 -0700	[thread overview]
Message-ID: <48EF9E2C.10000@oracle.com> (raw)
In-Reply-To: <20081010112356.b125bfb4.akpm@linux-foundation.org>

Andrew Morton wrote:
> On Fri, 10 Oct 2008 11:14:42 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> 
>> Andrew Morton wrote:
>>> On Fri, 10 Oct 2008 19:26:00 +0200 FD Cami <francois.cami@free.fr> wrote:
>>>
>>>> On Fri, 10 Oct 2008 09:34:27 -0700
>>>> Randy Dunlap <randy.dunlap@oracle.com> wrote:
>>>>
>>>>> On Fri, 10 Oct 2008 15:48:39 +0100 Alex Howells wrote:
>>>>>
>>>>>> Nick Warne wrote:
>>>>>>> Andrews' URL seems to be AWOL
>>>>>>>
>>>>>>> Documentation/SubmittingPatches: line 656
>>>>>>> <http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt>
>>>>>> The URL for -mm tree bisection was also missing and he mailed me a link.
>>>>>> Perhaps time to update the URLs generally?
>>>>> Would one of you send a patch, please?
>>> My zip account died for some reason.
>>>
>>>> Andrew, could you tell us where to find this now ?
>>> http://userweb.kernel.org/~akpm/stuff/tpp.txt                  <-----
>>>                                                                      \
>>>> That way we could update the URLs instead of removing them.         |
>>>                                                                      |
>>> We probably don't need the link at all - I think someone copied the  |
>>> guts of that doc into SubmittingPatches.                             |
>>                                                                        |
>> Do you have a current copy of tpp.txt so that we can check that?       |
>                                                                          /
>     ---------------------------------------------------------------------
> 
> :)

argh.  I had already looked there, before you added it.  Thanks.

-- 
~Randy

  reply	other threads:[~2008-10-10 18:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 14:15 Documentation error: SubmittingPatches Nick Warne
2008-10-10 14:48 ` Alex Howells
2008-10-10 16:34   ` Randy Dunlap
2008-10-10 17:26     ` FD Cami
2008-10-10 18:10       ` Andrew Morton
2008-10-10 18:14         ` Randy Dunlap
2008-10-10 18:23           ` Andrew Morton
2008-10-10 18:25             ` Randy Dunlap [this message]
2008-10-10 19:25         ` [PATCH] Remove Andrew Morton's old email accounts FD Cami
2008-10-10 19:48           ` Nick Warne
2008-10-10 20:26             ` Alex Howells
2008-10-10 21:26               ` FD Cami
2008-10-10 21:34                 ` Andrew Morton
2008-10-10 21:46                   ` Roland Dreier
2008-10-10 21:19         ` [PATCH] Remove Andrew Morton's http://www.zip.com.au/~akpm/ FD Cami
2008-10-10 21:56         ` [PATCH] Remove Andrew Morton's andrewm@uow.edu.au FD Cami

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=48EF9E2C.10000@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@bytemark.co.uk \
    --cc=francois.cami@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@ukfsn.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