From: Paul Jackson <pj@sgi.com>
To: Jeff Dike <jdike@addtoit.com>
Cc: Brice.Goglin@ens-lyon.fr, linux-kernel@vger.kernel.org
Subject: Re: uml-patch-2.6.0-test8
Date: Sat, 25 Oct 2003 06:37:37 -0700 [thread overview]
Message-ID: <20031025063737.5c4c1071.pj@sgi.com> (raw)
In-Reply-To: <200310250108.h9P18paK003981@ccure.karaya.com>
Your 2.6.0-test8 patch from:
http://jdike.stearns.org/mirror/uml-patch-2.6.0-test8.bz2
worked for me as well. It built and booted at least, when applied
to a clean, current as of a few hours ago:
bk://linux.bkbits.net/linux-2.5
But your bkbits tree, at:
http://jdike.stearns.org:5000/uml-2.5
seems to have something quite different in it than what
I got from the above linux-2.5 + uml-patch-2.6.0-test8.bz2.
Just one UML relevant example of what I see different:
================ arch/um/kernel/Makefile ================
48c50
< QUOTE = 'my $$config=`cat $(TOPDIR)/.config`; $$config =~ s/"/\\"/g ; while(<STDIN>) { $$_ =~ s/CONFIG/$$config/; print $$_ }'
---
> QUOTE = 'my $$config=`cat $(TOPDIR)/.config`; $$config =~ s/"/\\"/g ; $$config =~ s/\n/\\n"\n"/g ; while(<STDIN>) { $$_ =~ s/CONFIG/$$config/; print $$_ }'
The '<' is from your bkbits tree, and didn't compile.
The '>' is from applying your patch, and works.
I see many other differences as well, most seemgingly unrelated
to UML.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2003-10-25 13:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 8:37 uml-patch-2.6.0-test8 Brice Goglin
2003-10-25 1:08 ` uml-patch-2.6.0-test8 Jeff Dike
2003-10-25 13:37 ` Paul Jackson [this message]
2003-10-25 15:31 ` uml-patch-2.6.0-test8 Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 20:18 uml-patch-2.6.0-test8 Jeff Dike
2003-10-21 21:15 ` uml-patch-2.6.0-test8 Jeff Dike
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=20031025063737.5c4c1071.pj@sgi.com \
--to=pj@sgi.com \
--cc=Brice.Goglin@ens-lyon.fr \
--cc=jdike@addtoit.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
Powered by JetHome