From: Sam Ravnborg <sam@ravnborg.org>
To: Ingo Molnar <mingo@elte.hu>
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: Tue, 8 Jan 2008 23:17:22 +0100 [thread overview]
Message-ID: <20080108221722.GA27698@uranus.ravnborg.org> (raw)
In-Reply-To: <20080108215247.GE14829@elte.hu>
> > Most of these kernel changes would probably get in the way of real
> > development, making patches reject that would otherwise apply.
>
> I'm curious, in what way would they interfere?
Developer A work one some complicated stuff in foo.c which is
not yet -mm fooder.
Developer B submits and have applied a massive cleanup to some of the
files touced by Developer A's patch.
Developer A now needs to fix up his stuff.
Reminder: Not everyone writes their stuff in 48 hours before it
is lkml ready.
>
> 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?
Sam
next prev parent reply other threads:[~2008-01-08 22:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 19:32 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 [this message]
2008-01-08 22:35 ` Ingo Molnar
2008-01-08 23:57 ` Sam Ravnborg
2008-01-09 0:15 ` Ingo Molnar
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=20080108221722.GA27698@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=riel@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome