public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Srihari Vijayaraghavan <harisri@bigpond.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20pre11aa1
Date: Tue, 22 Oct 2002 16:55:28 +0200	[thread overview]
Message-ID: <20021022145528.GW19337@dualathlon.random> (raw)
In-Reply-To: <200210222048.05592.harisri@bigpond.com>

On Tue, Oct 22, 2002 at 08:48:05PM +1000, Srihari Vijayaraghavan wrote:
> Hello Andrea,
> 
> On Saturday 19 October 2002 11:25, Andrea Arcangeli wrote:
> > that will help a lot, thanks!
> 
> Is there a quick HOWTO on how to apply the individual patches?
> 
> Do I apply 00*gz patches after applying 00* patches?

gz doesn't matter, the `ls` ordering is the only thing that matters. You
can gzip -d * and then apply [0123]* and see if it still breaks.

> When I tried the above procedure there were a lot of hunks and it did not 
> compile bzImage and agpgart.o etc..

something like this will apply cleanly, if every patch is self contained
as it should, it will compile correctly too:

	rm ../2.4.20pre11aa1/*.bz2
	gzip -d ../2.4.20pre11aa1/*.gz
	for i in ../2.4.20pre11aa1/[0123]*; patch -p1 < $i; done

Andrea

  reply	other threads:[~2002-10-22 14:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 16:51 2.4.20pre11aa1 Andrea Arcangeli
2002-10-17 12:04 ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 12:10   ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-17 13:01     ` 2.4.20pre11aa1 Keith Owens
2002-10-17 15:26       ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 16:27         ` 2.4.20pre11aa1 Andrea Arcangeli
     [not found]           ` <200210190014.19357.harisri@bigpond.com>
2002-10-18 14:52             ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-18 15:21               ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-18 15:34               ` 2.4.20pre11aa1 Keith Owens
2002-10-18 16:00                 ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-19  1:21                   ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-19  1:25                     ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-22 10:48                       ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-22 14:55                         ` Andrea Arcangeli [this message]
2002-10-23 12:27                           ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-23 12:46                             ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-23 14:26                               ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-23 14:35                                 ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-25 14:03                                   ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-31 10:47                                     ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-11-09  9:34                                       ` Solved 2.4.20pre11aa1/2.4.20rc1aa1 Agpgart/Radeon crash. [was: Re: 2.4.20pre11aa1] Srihari Vijayaraghavan
2002-11-10  2:50                                         ` Andrea Arcangeli
2002-11-10  3:24                                           ` Srihari Vijayaraghavan
2002-10-17 13:02     ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 13:00       ` 2.4.20pre11aa1 Andrea Arcangeli

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=20021022145528.GW19337@dualathlon.random \
    --to=andrea@suse.de \
    --cc=harisri@bigpond.com \
    --cc=linux-kernel@vger.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