From: Chris Wedgwood <cw@f00f.org>
To: Blaisorblade <blaisorblade_spam@yahoo.it>
Cc: akpm@osdl.org, user-mode-linux-devel@lists.sourceforge.net,
LKML <linux-kernel@vger.kernel.org>,
jdike@addtoit.com
Subject: [uml-devel] Re: [patch 7/7] uml: resolve symbols in back-traces
Date: Thu, 28 Oct 2004 14:43:47 -0700 [thread overview]
Message-ID: <20041028214347.GC2269@taniwha.stupidest.org> (raw)
In-Reply-To: <200410282302.48311.blaisorblade_spam@yahoo.it>
On Thu, Oct 28, 2004 at 11:02:48PM +0200, Blaisorblade wrote:
> If Jeff says "OK", then someone can submit a separate patch removing
> all the final comments.
he did
> And never mix such unrelated changes in a patch.
idealistically i agree, but doing trivial / obvious cleanups inside
other patches is fine if you ask me
it's not like we are mixing semantically different changes
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
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-10-28 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410272223.i9RMNj921852@mail.osdl.org>
2004-10-28 18:34 ` [uml-devel] Re: [patch 7/7] uml: resolve symbols in back-traces Blaisorblade
2004-10-28 19:28 ` Chris Wedgwood
2004-10-28 21:02 ` Blaisorblade
2004-10-28 21:43 ` Chris Wedgwood [this message]
2004-10-28 21:32 ` Jeff Dike
2004-10-28 20:51 ` Chris Wedgwood
2004-10-28 23:44 ` Blaisorblade
2004-10-29 0:19 ` Chris Wedgwood
2004-10-28 23:42 ` Blaisorblade
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=20041028214347.GC2269@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=akpm@osdl.org \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--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