From: Jeff Dike <jdike@addtoit.com>
To: "Stroesser, Bodo" <Bodo.Stroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: Re: [uml-devel] Syscalls breaking out
Date: Fri, 24 Sep 2004 15:10:25 -0400 [thread overview]
Message-ID: <200409241910.i8OJAPZX003320@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 24 Sep 2004 15:39:44 +0200." <8B6FF516CBA0194AB0996705076B02520F7C39@ABGEX01E.abg.fsc.net>
Bodo.Stroesser@fujitsu-siemens.com said:
> (It would overlap with my previos patch, should I merge them?)
I'm looking at your patches and will get back to you on them, but let me just
comment on this issue first.
I'd prefer these patches be split up into as small units as possible. That'll
make it easier to decide whether they are correct. It's OK if they overlap
and need to be applied in a particular order.
So, for example, the API changes could be broken out separately. Even if it's
two lines of change (the caller and the callee), that's a good way to split it
up. This part of the kernel has some subtleties, so I'd prefer to be careful
here.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-09-24 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 13:39 [uml-devel] Syscalls breaking out Stroesser, Bodo
2004-09-24 19:10 ` Jeff Dike [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 18:52 Stroesser, Bodo
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=200409241910.i8OJAPZX003320@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=Bodo.Stroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@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