From: Rob Landley <rob@landley.net>
To: Ben Minerds <puzzleduck@gmail.com>
Cc: greg@kroah.com, Ben Minerds <PuZZleDucK@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] Documentation: Updating a broken link in "the perfect patch"
Date: Thu, 23 May 2013 23:21:26 -0500 [thread overview]
Message-ID: <1369369286.2776.16@driftwood> (raw)
In-Reply-To: <95e6b8218195f2be60823ce6de5ea524b727fe11.1369312746.git.PuZZleDucK@gmail.com> (from puzzleduck@gmail.com on Thu May 23 07:49:58 2013)
On 05/23/2013 07:49:58 AM, Ben Minerds wrote:
> The link to Andrews patches were out of date. Replacing with new
> links. Also
> slightly reformatted to allow easier selection of links.
>
> Signed-off-by: Ben Minerds <puzzleduck@gmail.com>
> ---
> Documentation/development-process/patches/The-Perfect-Patch.txt | 8
> ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git
> a/Documentation/development-process/patches/The-Perfect-Patch.txt
> b/Documentation/development-process/patches/The-Perfect-Patch.txt
> index 217a303..63eccbb 100644
> --- a/Documentation/development-process/patches/The-Perfect-Patch.txt
> +++ b/Documentation/development-process/patches/The-Perfect-Patch.txt
> @@ -160,8 +160,8 @@ Overall
>
>
>
> -The patch management scripts at
> http://www.zip.com.au/~akpm/linux/patches/
> -implement all of the above.
> +The patch management scripts here implement all of the above:
> + https://www.kernel.org/pub/linux/kernel/people/akpm/patches/
I looked in that directory, and I'm not seeing quilt.
> -The patch management tools at
> https://savannah.nongnu.org/projects/quilt/ also
> -implement all of the above.
> \ No newline at end of file
> +The patch management tools here implement all of the above:
> + https://savannah.nongnu.org/projects/quilt/
This appears to be the currently location. As mentioned on line 76 of
the current Documentation/SubmittingPatches.
I think I'd like to NAK this whole series until you read what's
currently in the tree, please?
Rob
next prev parent reply other threads:[~2013-05-24 4:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 12:49 [PATCH 0/8] Documentation: Updating docs and links relating to patches Ben Minerds
2013-05-23 12:49 ` [PATCH 1/8] Documentation: Adding "The Perfect Patch" by Andrew Morton Ben Minerds
2013-05-23 17:15 ` Dave Jones
2013-05-24 4:10 ` Rob Landley
2013-05-24 4:16 ` Joe Perches
2013-05-23 12:49 ` [PATCH 2/8] Documentation: Adding "Linux Kernel Patch Submission Format" Ben Minerds
2013-05-24 4:12 ` Rob Landley
2013-05-23 12:49 ` [PATCH 3/8] Documentation: Replacing references to broken perfect patch URL Ben Minerds
2013-05-23 12:49 ` [PATCH 4/8] Documentation: Replacing reference " Ben Minerds
2013-05-23 12:49 ` [PATCH 5/8] Documentation: Replacing reference to broken submission format URL Ben Minerds
2013-05-24 4:16 ` Rob Landley
2013-05-23 12:49 ` [PATCH 6/8] Documentation: Updating a broken link in "the perfect patch" Ben Minerds
2013-05-24 4:21 ` Rob Landley [this message]
2013-05-23 12:49 ` [PATCH 7/8] Documentation: Reformatting "Linux Kernel Patch Submission Format" Ben Minerds
2013-05-23 12:50 ` [PATCH 8/8] Documentation: Move other patch related document Ben Minerds
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=1369369286.2776.16@driftwood \
--to=rob@landley.net \
--cc=greg@kroah.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=puzzleduck@gmail.com \
/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