From: Andrew Morton <akpm@osdl.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net, 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 08:44:30 -0700 [thread overview]
Message-ID: <20060429084430.27ea0d91.akpm@osdl.org> (raw)
In-Reply-To: <200604291641.19864.blaisorblade@yahoo.it>
Blaisorblade <blaisorblade@yahoo.it> wrote:
>
> > 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.
Lindent doesn't do a terribly good job, and one ends up having to perform a
lot of manual fixups. Perhaps as many as are presently needed.
next prev parent reply other threads:[~2006-04-29 15:46 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 ` [uml-devel] " Blaisorblade
2006-04-29 15:44 ` Andrew Morton [this message]
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=20060429084430.27ea0d91.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=blaisorblade@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
Powered by JetHome