From: Jeff Dike <jdike@addtoit.com>
To: "J. Cone" <jcone@eservglobal.com>
Cc: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] Fwd: mrproper and debug
Date: Mon, 06 Oct 2003 17:24:50 -0400 [thread overview]
Message-ID: <200310062124.h96LOoGj020838@ccure.karaya.com> (raw)
In-Reply-To: Your message of "Thu, 02 Oct 2003 19:12:42 +1200." <4.3.2.7.0.20031002191200.016f0f00@mail>
jcone@eservglobal.com said:
> I haven't yet seen this in the list or the archive, so I'm trying
> again.
I hit both these problems recently. I fixed the nasty math the same way
you did, except with slightly more sane values of the CONFIG vaiables :-)
I hadn't dealt with the DEBUG_INFO one yet, but was contemplating something
like what you did.
Jeff
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
parent reply other threads:[~2003-10-06 21:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4.3.2.7.0.20031002191200.016f0f00@mail>]
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=200310062124.h96LOoGj020838@ccure.karaya.com \
--to=jdike@addtoit.com \
--cc=jcone@eservglobal.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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