From: Johannes Stezenbach <js@linuxtv.org>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
Rolf Eike Beer <eike-kernel@sf-tec.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sean Bruno <sean.bruno@dsl-only.net>,
Lee Revell <rlrevell@joe-job.com>, Bodo Eggert <7eggert@gmx.de>,
Gene Heskett <gene.heskett@verizon.net>,
"H. Peter Anvin" <hpa@zytor.com>,
David Brown <dmlb2000@gmail.com>,
Puneet Vyas <vyas.puneet@gmail.com>,
Richard Hubbell <richard.hubbell@gmail.com>,
webmaster@kernel.org
Subject: Re: Documentation - how to apply patches for various trees
Date: Thu, 4 Aug 2005 01:56:39 +0200 [thread overview]
Message-ID: <20050803235639.GC6223@linuxtv.org> (raw)
In-Reply-To: <200508032328.07727.jesper.juhl@gmail.com>
On Wed, Aug 03, 2005 Jesper Juhl wrote:
> +How do I feed a patch/diff file to `patch'?
> +---
> + This (as usual with Linux and other UNIX like operating systems) can be
> +done in several different ways.
> +In all the examples below I feed the file (in uncompressed form) to patch
> +via stdin using the following syntax:
> + patch -p1 < path/to/patch-x.y.z
I think you should mention the -s flag. Given the size of an
average kernel patch it is otherwise very likely that errors scroll
away unnoticed.
OTOH you might also want to add a mention of lsdiff and diffstat.
Johannes
next prev parent reply other threads:[~2005-08-03 23:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 21:32 Documentation - how to apply patches for various trees Jesper Juhl
2005-08-02 22:38 ` Randy.Dunlap
2005-08-03 1:05 ` Richard Hubbell
2005-08-03 2:00 ` Puneet Vyas
2005-08-03 6:40 ` Rolf Eike Beer
2005-08-03 14:44 ` Randy.Dunlap
[not found] ` <200508032251.07996.jesper.juhl@gmail.com>
2005-08-03 21:08 ` Linus Torvalds
2005-08-03 21:28 ` Jesper Juhl
2005-08-03 23:56 ` Johannes Stezenbach [this message]
2005-08-04 0:33 ` Grant Coady
2005-08-04 7:44 ` Rolf Eike Beer
2005-08-05 22:52 ` Jesper Juhl
2005-08-03 21:46 ` Bodo Eggert
2005-08-03 23:19 ` Jesper Juhl
2005-08-03 11:50 ` Pavel Machek
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=20050803235639.GC6223@linuxtv.org \
--to=js@linuxtv.org \
--cc=7eggert@gmx.de \
--cc=akpm@osdl.org \
--cc=dmlb2000@gmail.com \
--cc=eike-kernel@sf-tec.de \
--cc=gene.heskett@verizon.net \
--cc=hpa@zytor.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=richard.hubbell@gmail.com \
--cc=rlrevell@joe-job.com \
--cc=rostedt@goodmis.org \
--cc=sean.bruno@dsl-only.net \
--cc=torvalds@osdl.org \
--cc=vyas.puneet@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.