From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: backtrace support
Date: Fri, 19 Aug 2005 03:01:35 +0200 [thread overview]
Message-ID: <200508190301.35298.okuji@enbug.org> (raw)
In-Reply-To: <4304FB6C.1020600@inma.ucl.ac.be>
On Thursday 18 August 2005 23:19, Vincent Guffens wrote:
> cool ! I will wait a little bit for your comments and those from Okuji
> as there are a few changes I made that I'm not sure if they are very
> clean, especially those in genmk.rb.
Good job, Vincent.
> I used some "cat config.h" and
> maybe there are some better ways.
Possibly you can substitute a variable in Makefile.in and use the variable.
> Should the Changelog entries be included in the patch or is it generated
> with the cvs log and it should then be sent in the mail body ?
ChangeLog must be handwritten. As long as it is written well, I don't care
about how you send it. Using the Change Log mode in Emacs would help you a
lot.
It is still necessary to clean up the patch. Running make twice does not sound
good. One easy way is to build a separate backtrace module outside the
kernel, and load it as soon as possible, like the normal module.
Also, I think it would be better to rename --enable-backtrace to
--enable-debug, so that we can enable all debugging features by one option
(when we get more debugging features, this could be useful).
Okuji
next prev parent reply other threads:[~2005-08-19 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 20:22 backtrace support Vincent Guffens
2005-08-18 20:58 ` Marco Gerards
2005-08-18 21:19 ` Vincent Guffens
2005-08-19 1:01 ` Yoshinori K. Okuji [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-22 21:23 Vincent Guffens
2005-08-23 7:46 ` Vincent Pelletier
2005-08-28 12:49 ` Yoshinori K. Okuji
2005-08-29 9:47 ` Vincent Guffens
2005-08-28 13:47 ` Marco Gerards
2005-08-29 11:20 ` Vincent Guffens
2005-08-31 19:01 ` Marco Gerards
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=200508190301.35298.okuji@enbug.org \
--to=okuji@enbug.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.