Re: Documentation - how to apply patches for various trees

[Grant Coady <lkml@dodo.com.au>]

Hi Jesper,
On Wed, 3 Aug 2005 23:28:06 +0200, Jesper Juhl <jesper.juhl@gmail.com> wrote:

I like it, just a little concerned about confusing new user with too 
many alternative patching methods up front...

>+ 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
>+
>+but patch can also get the name of the file to use via the -i argument, like
>+this:
>+	patch -p1 -i path/to/patch-x.y.z
>+
>+If your patch file is compressed with gzip or bzip2 and you don't want to
>+uncompress it before applying it, then you can feed it to patch like this
>+instead:

	cat path/to/patch-x.y.z.gz | patch -p1
>+	zcat path/to/patch-x.y.z.gz | patch -p1
>+	bzcat path/to/patch-x.y.z.bz2 | patch -p1

In a howto, I'd prefer  _one_ consistent method to reduce the 
reader's confusion.  

The above trio of commands serves me well over many years' kernel 
patching, and it is trivial to up-arrow, home, change compression 
method, retry ... when my fingers get ahead of my mind :)


Experience users recognise the intent of the commands and use their 
favourite method instead, almost without thinking.


Spelling:

s/uncompression/decompression/
s/adviced/advised/
s/bandwith/bandwidth/

Cheers,
Grant.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/