All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Rik van Riel <riel@redhat.com>,
	Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
	tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	trivial@kernel.org
Subject: Re: [PATCH 3/5] x86: coding style fixes in arch/x86/ia32/ia32_aout.c
Date: Wed, 9 Jan 2008 01:15:55 +0100	[thread overview]
Message-ID: <20080109001555.GA31289@elte.hu> (raw)
In-Reply-To: <20080108235719.GA28353@uranus.ravnborg.org>


* Sam Ravnborg <sam@ravnborg.org> wrote:

> > > > Firstly, anyone with a forked kernel with outstanding patches 
> > > > that are not in x86.git only has themselves to blame. We want to 
> > > > actively discourage forking and sitting on patches too long.
> > > 
> > > Curious - what is the purpose of the x86.git tree these days?
> > 
> > what do want to imply by 'these days'?
> 
> I wondered when you wrote "anyone with a forked kernel with 
> outstanding patches that are not in x86.git" if this was only x86 
> specific patches or more than that. I could have a slev of patches in 
> the works for parts that are no x86 specific (which I unfortunately do 
> not have).

ah, i now understand what you mean. The stuff in -mm that touches 
arch/x86 is for actively maintained areas which are generally quite 
clean.

So this is not a problem in practice - massively unclean areas of code, 
which are the primary target for cleanups, are not actively developed. [ 
perhaps because there's some level of correlation between unclean code 
and lack of developer interest :-/ ]

	Ingo

  reply	other threads:[~2008-01-09  0:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 19:32 [PATCH 3/5] x86: coding style fixes in arch/x86/ia32/ia32_aout.c Paolo Ciarrocchi
2008-01-08 19:59 ` Alexey Dobriyan
2008-01-08 20:04 ` Rik van Riel
2008-01-08 20:51   ` Sam Ravnborg
2008-01-08 21:52   ` Ingo Molnar
2008-01-08 22:17     ` Sam Ravnborg
2008-01-08 22:35       ` Ingo Molnar
2008-01-08 23:57         ` Sam Ravnborg
2008-01-09  0:15           ` Ingo Molnar [this message]
2008-01-08 22:55       ` Jiri Slaby

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=20080109001555.GA31289@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paolo.ciarrocchi@gmail.com \
    --cc=riel@redhat.com \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=trivial@kernel.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.