From: "H. Peter Anvin" <hpa@zytor.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Jesper Juhl <jesper.juhl@gmail.com>, Greg KH <greg@kroah.com>,
Nick Warne <nick@linicks.net>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, webmaster@kernel.org
Subject: Re: 2.6.14.5 to 2.6.15 patch
Date: Thu, 05 Jan 2006 08:42:55 -0800 [thread overview]
Message-ID: <43BD4C8F.3040703@zytor.com> (raw)
In-Reply-To: <200601051555.25915.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
>>
>>Nice writeup, but why not simply put a copy of
>>Documentation/applying-patches.txt online and link to that?
>>It contains more or less the same stuff you just wrote.
>
> It's certainly one possibility, but this file is at least 4x more verbose than
> my summary. I aimed to write something instructional, rather than provide a
> complete explanation of the "patch problem".
>
> If this issue is large enough to get its own page on kernel.org, then a more
> complete description may indeed be justified. Comments?
>
It'd be easy to make its own page, and then link it from the FAQ. Heck,
the easiest might be to link it to the gitweb checkout of
Documentation/applying-patches.txt, but having it be nicely HTML
formatted would probably be better.
-hpa
next prev parent reply other threads:[~2006-01-05 16:43 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 17:10 2.6.14.5 to 2.6.15 patch Nick Warne
2006-01-04 17:18 ` Jesper Juhl
2006-01-04 17:28 ` Nick Warne
2006-01-04 17:36 ` Randy.Dunlap
2006-01-04 17:39 ` Nick Warne
2006-01-04 18:34 ` Alistair John Strachan
2006-01-04 19:53 ` Nick Warne
2006-01-04 20:10 ` Alistair John Strachan
2006-01-04 22:01 ` Greg KH
2006-01-04 22:10 ` Nick Warne
2006-01-04 22:15 ` Greg KH
2006-01-04 22:20 ` Nick Warne
2006-01-04 22:30 ` Greg KH
2006-01-04 22:30 ` Jesper Juhl
2006-01-04 22:36 ` Nick Warne
2006-01-04 23:10 ` Greg KH
2006-01-04 22:49 ` Grant Coady
2006-01-04 22:16 ` Randy.Dunlap
2006-01-04 22:31 ` Greg KH
2006-01-04 22:58 ` Alistair John Strachan
2006-01-04 23:13 ` Greg KH
2006-01-04 23:28 ` Alistair John Strachan
2006-01-04 23:31 ` Randy.Dunlap
2006-01-04 23:41 ` Greg KH
2006-01-04 23:42 ` Randy.Dunlap
2006-01-04 23:49 ` Jesper Juhl
2006-01-05 7:30 ` Jan Engelhardt
2006-01-04 22:49 ` Alistair John Strachan
2006-01-04 23:12 ` Greg KH
2006-01-04 23:26 ` Alistair John Strachan
2006-01-05 0:08 ` H. Peter Anvin
2006-01-05 15:25 ` Alistair John Strachan
2006-01-05 15:37 ` Jesper Juhl
2006-01-05 15:55 ` Alistair John Strachan
2006-01-05 16:42 ` H. Peter Anvin [this message]
2006-01-04 20:10 ` Matan Peled
2006-01-04 22:01 ` Greg KH
2006-01-04 22:50 ` Alistair John Strachan
2006-01-04 17:40 ` Jesper Juhl
2006-01-04 17:45 ` Nick Warne
2006-01-04 17:50 ` Jesper Juhl
2006-01-04 17:51 ` Randy.Dunlap
2006-01-04 17:56 ` Jesper Juhl
2006-01-04 18:08 ` Mark Lord
2006-01-04 18:13 ` Jesper Juhl
2006-01-04 21:13 ` Grant Coady
2006-01-04 21:20 ` Jesper Juhl
2006-01-04 17:56 ` Nick Warne
2006-01-04 18:27 ` Steven Rostedt
2006-01-04 21:17 ` Jesper Juhl
2006-01-04 21:48 ` Steven Rostedt
2006-01-04 22:20 ` Steven Rostedt
2006-01-04 17:19 ` Marc Haber
2006-01-04 17:29 ` Steven Rostedt
2006-01-04 17:29 ` YOSHIFUJI Hideaki / 吉藤英明
2006-01-04 18:15 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2006-01-05 17:14 mreuther
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=43BD4C8F.3040703@zytor.com \
--to=hpa@zytor.com \
--cc=greg@kroah.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
--cc=rdunlap@xenotime.net \
--cc=s0348365@sms.ed.ac.uk \
--cc=webmaster@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