All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Matt Mackall <mpm@selenic.com>, Pavel Machek <pavel@ucw.cz>,
	"Marcos D. Marado Torres" <marado@student.dei.uc.pt>,
	Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, chrisw@osdl.org, torvalds@osdl.org,
	akpm@osdl.org
Subject: Re: Linux 2.6.11.2
Date: Wed, 16 Mar 2005 08:56:16 +0000	[thread overview]
Message-ID: <4237F4B0.2040509@dgreaves.com> (raw)
In-Reply-To: <423747BC.2080703@tmr.com>

Bill Davidsen wrote:

> Matt Mackall wrote:
>
>> In your world, do you want to do:
>>
>> cp -rl linux-2.6.11 linux-2.6.11.5
>> cd linux-2.6.11.5
>> bzcat ../Patches/patch-2.6.11.1.bz2 | patch -p1
>> bzcat ../Patches/patch-2.6.11.2.bz2 | patch -p1
>> bzcat ../Patches/patch-2.6.11.3.bz2 | patch -p1
>> bzcat ../Patches/patch-2.6.11.4.bz2 | patch -p1
>> bzcat ../Patches/patch-2.6.11.5.bz2 | patch -p1
>>
>> I suspect you might find that tedious, especially if only the last one
>> addressed a bug that affected you.
>
>
> Being lazy, I would do
> bzcat ../Patches/patch-2.6.11.*.bz | patch -p1
> (or similar). But as I posted long ago when this discussion started it 
> is desirable to have both.
>
being super lazy I'd type:
scripts/patch-kernel . ../Patches

nb it's currently broke as mentioned in another thread:
Re: [BUG] Re: [PATCH] scripts/patch-kernel: use EXTRAVERSION
being fixed though. It will (I assume!) embody whatever rules are needed 
to revoke patches to go from 2.6.11.5 to 2.6.12 (and since I think the 
new version has d/l facilities, that should assist in the case of a base 
kernel d/l of 2.6.11.3 for which no local patches exist to revert prior 
to patching to 2.6.12)

David



  reply	other threads:[~2005-03-16  8:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  8:39 Linux 2.6.11.2 Greg KH
2005-03-09  8:39 ` Greg KH
2005-03-17 15:18   ` Gene Heskett
2005-03-09  9:52 ` Marcos D. Marado Torres
2005-03-09 10:04   ` Geert Uytterhoeven
2005-03-09 10:17     ` Marcos D. Marado Torres
2005-03-09 10:41       ` Geert Uytterhoeven
2005-03-09 11:23         ` Jesper Juhl
2005-03-09 21:26       ` Wakko Warner
2005-03-09 10:21     ` Dominik Karall
2005-03-09 10:28       ` Marcos D. Marado Torres
2005-03-09 10:51         ` Adrian Bunk
2005-03-09 15:35         ` Greg KH
2005-03-09 11:11   ` Pavel Machek
2005-03-09 23:57     ` Matt Mackall
2005-03-10  5:16       ` Willy Tarreau
2005-03-11 18:45       ` Bill Davidsen
2005-03-11 19:08         ` Matt Mackall
2005-03-11 19:19           ` Chris Wright
2005-03-11 22:01             ` Greg KH
2005-03-14 17:10               ` Bill Davidsen
2005-03-14 17:32                 ` Greg KH
2005-03-15 20:38           ` Bill Davidsen
2005-03-16  8:56             ` David Greaves [this message]
2005-03-09 12:38 ` Andy Whitcroft
2005-03-09 14:03 ` Marcelo Tosatti
2005-03-09 18:38   ` Greg KH
2005-03-09 20:32 ` Bill Davidsen
2005-03-09 21:06 ` Matt Mackall
2005-03-09 21:21   ` Randy.Dunlap
2005-03-09 23:11   ` Greg KH
2005-03-09 23:38     ` Matt Mackall
2005-03-10 12:54     ` Gene Heskett
2005-03-11 19:23       ` Bill Davidsen
2005-03-11 23:33         ` Gene Heskett
2005-03-11 14:53 ` Krzysztof Halasa
2005-03-11 17:38   ` Chris Wright
2005-03-11 19:28     ` Bill Davidsen
2005-03-11 21:07     ` Krzysztof Halasa
2005-03-11 21:11       ` Chris Wright
     [not found] <fa.dan38um.1m4gojq@ifi.uio.no>
     [not found] ` <fa.animhpl.r201hh@ifi.uio.no>
2005-03-10  1:46   ` Bodo Eggert
2005-03-10  3:08     ` Matt Mackall

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=4237F4B0.2040509@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=davidsen@tmr.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marado@student.dei.uc.pt \
    --cc=mpm@selenic.com \
    --cc=pavel@ucw.cz \
    --cc=torvalds@osdl.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.