From: Adam Schrotenboer <ajschrotenboer@lycosmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux ac20 patch got error:
Date: Thu, 22 Feb 2001 11:21:20 -0500 [thread overview]
Message-ID: <3A953C80.9030609@lycosmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0102220543240.1500-100000@mikeg.weiden.de>
Mike Galbraith wrote:
> On Wed, 21 Feb 2001, Adam Schrotenboer wrote:
>
>> A rather incomprehensible message, so let's flesh this out a bit.
>>
>> Basically the problem occurs when patching linux/fs/reiserfs/namei.c It
>> can't find it, presumably due to an error in 2.4.1, where it appears to
>> me that reiserfs/ is located off of linux/ not linux/fs/. Simple to fix,
>> I guess, though this would appear to mean that Linus made a mistake w/
>> 2.4.1 (plz correct me if I'm wrong), though it could also be said that
>> this means that Alan diff'd the wrong tree (basically a fixed tree in re
>> reiserfs/)
>
>
> A third possibility: an elf/gremlin munged your tree for grins ;-)
maybe I coffed. 8-)
>
> ac20 went in clean here.
>
> -Mike
Granted that this is possible, yet how likely is it that two people
would come up with the same problem, when they don't even know each
other. 2nd, this was a fresh tree, i.e. 2.4.0 from tar.bz2, patch to
2.4.1, then patch to 2.4.1-ac20, therefore there likely must be
something else. Maybe a similarly corrupted (shouldn't be possible w/
bz2, let alone gz) 2.4.1 patch, or some such. Still, given that it was a
d/l from zeus.kernel.org, it should be ok (short of somebody hacking the
server. I rarely check the sigs)
next prev parent reply other threads:[~2001-02-22 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 18:38 linux ac20 patch got error: Adam Schrotenboer
2001-02-22 4:48 ` Mike Galbraith
2001-02-22 16:21 ` Adam Schrotenboer [this message]
2001-02-22 18:23 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2001-02-21 14:12 Thomas Lau
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=3A953C80.9030609@lycosmail.com \
--to=ajschrotenboer@lycosmail.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