From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-rc6-mm1
Date: Mon, 11 Sep 2006 17:56:26 -0400 [thread overview]
Message-ID: <200609111759_MC3-1-CAE8-1802@compuserve.com> (raw)
In-Reply-To: <20060911102328.861a64b3.akpm@osdl.org>
On Mon, 11 Sep 2006 10:23:28 -0700, Andrew Morton wrote:
> wget ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.18-rc6.tar.bz2
> wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc6/2.6.18-rc6-mm1/2.6.18-rc6-mm1-broken-out.tar.gz
> box:/home/akpm> mkdir aa
> box:/home/akpm> cd aa
> box:/home/akpm/aa> tar xfj ../linux-2.6.18-rc6.tar.bz2
> box:/home/akpm/aa> cd linux-2.6.18-rc6
> box:/home/akpm/aa/linux-2.6.18-rc6> tar xfz ../../2.6.18-rc6-mm1-broken-out.tar.gz
> box:/home/akpm/aa/linux-2.6.18-rc6> mv broken-out patches
> box:/home/akpm/aa/linux-2.6.18-rc6> quilt push -a > /dev/null
> box:/home/akpm/aa/linux-2.6.18-rc6> quilt applied | wc -l
> 1835
I found the problem:
$ set | fgrep QUILT
QUILT_DIFF_OPTS=-p
QUILT_PATCH_OPTS=--fuzz=0
^^^^^^^^
Your patchset does have conflicts -- you're just ignoring them
by accepting fuzz (and patch hunks can even end up being applied
at the wrong place.)
--
Chuck
next reply other threads:[~2006-09-11 22:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 21:56 Chuck Ebbert [this message]
2006-09-11 22:35 ` 2.6.18-rc6-mm1 Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2006-09-11 12:41 2.6.18-rc6-mm1 Chuck Ebbert
2006-09-11 17:23 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-11 2:34 2.6.18-rc6-mm1 Chuck Ebbert
2006-09-11 5:14 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-09 12:45 2.6.18-rc6-mm1 Magnus Määttä
2006-09-09 18:27 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-10 0:37 ` 2.6.18-rc6-mm1 Magnus Määttä
2006-09-10 5:35 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-10 10:22 ` 2.6.18-rc6-mm1 Magnus Määttä
2006-09-13 4:54 ` 2.6.18-rc6-mm1 Neil Brown
2006-09-16 14:10 ` 2.6.18-rc6-mm1 Magnus Määttä
2006-09-08 8:13 2.6.18-rc6-mm1 Andrew Morton
2006-09-08 11:49 ` 2.6.18-rc6-mm1 Andy Whitcroft
2006-09-08 12:07 ` 2.6.18-rc6-mm1 Frederik Deweerdt
2006-09-08 14:26 ` 2.6.18-rc6-mm1 Rafael J. Wysocki
2006-09-08 17:43 ` 2.6.18-rc6-mm1 Stefan Richter
2006-09-08 18:04 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-08 18:36 ` 2.6.18-rc6-mm1 Stefan Richter
2006-09-08 19:23 ` 2.6.18-rc6-mm1 Michal Piotrowski
2006-09-08 19:43 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-08 20:01 ` 2.6.18-rc6-mm1 Michal Piotrowski
2006-09-08 19:30 ` 2.6.18-rc6-mm1 thunder7
2006-09-08 19:44 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-09 9:04 ` 2.6.18-rc6-mm1 thunder7
2006-09-09 15:31 ` 2.6.18-rc6-mm1 Andrew Morton
2006-09-09 22:02 ` 2.6.18-rc6-mm1 Jean Delvare
2006-09-10 6:30 ` 2.6.18-rc6-mm1 thunder7
2006-09-11 21:19 ` 2.6.18-rc6-mm1 Mark Haverkamp
2006-09-11 22:16 ` 2.6.18-rc6-mm1 Andrew Morton
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=200609111759_MC3-1-CAE8-1802@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®