From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>, Jeff Dike <jdike@addtoit.com>,
linux-kernel@vger.kernel.org
Subject: Re: [uml-devel] Re: [PATCH 0/6] UML - Small patches for 2.6.17
Date: Sat, 29 Apr 2006 16:41:18 +0200 [thread overview]
Message-ID: <200604291641.19864.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060428165534.6067f5aa.akpm@osdl.org>
On Saturday 29 April 2006 01:55, Andrew Morton wrote:
> Jeff Dike <jdike@addtoit.com> wrote:
> > These patches are 2.6.17 material.
>
> "remove NULL checks and add some CodingStyle" isn't.
Being restrictive is ok, but keeping patches in queues for longer than needed
creates more headaches than it solves, in my experience.
> Unless one considers
> UML coding style to be a bug, which is an attractive idea ;)
Well, we're slowly working on that... very slowly... I've thought multiple
times to at least run Lindent on arch/um but I've not spoken up because of
all the conflicts we (me and Jeff) would get with patches in our queues.
However, there are occasions in which we get conflicts anyway for other
reorganization, and in that case Lindent would be useful. Ok Jeff? I'm
speaking for instance about moving to os-Linux and such.
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
next prev parent reply other threads:[~2006-04-29 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 16:01 Jeff Dike
2006-04-28 23:55 ` Andrew Morton
2006-04-29 14:41 ` Blaisorblade [this message]
2006-04-29 15:44 ` [uml-devel] " Andrew Morton
2006-05-01 16:46 ` 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=200604291641.19864.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--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
Powered by JetHome