From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Dave Jones <davej@codemonkey.org.uk>, Robert Love <rml@tech9.net>,
Tim Schmielau <tim@physik3.uni-rostock.de>,
John Levon <levon@movementarian.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] break out task_struct from sched.h
Date: Sun, 29 Sep 2002 19:23:54 -0300 [thread overview]
Message-ID: <20020929222353.GC7028@conectiva.com.br> (raw)
In-Reply-To: <20020929221725.GA7557@suse.de>
Em Sun, Sep 29, 2002 at 11:17:25PM +0100, Dave Jones escreveu:
> On Sun, Sep 29, 2002 at 05:06:29PM -0400, Robert Love wrote:
> > > Killing ~600 #include <linux/sched.h> lines however seemed enough for a
> > > first round, so I left this for later iterations.
> > Indeed, good job.
> Seconded. Worth noting that Tim first did this months ago,
> and has been keeping this up to date since. These large patches
> that touch lots of areas go stale very quickly and are always
> a real pain to maintain, and merge. It'd be good if people can
> beat up on this patch a little to catch the more obvious
> compile errors that always result in large shake ups like this.
> Then theres the daily sending to Linus until he takes it 8)
Tim, thanks for the good work, I'm with Dave, lets beat this one a bit
and then start sending it regularly to Linus.
- Arnaldo
next prev parent reply other threads:[~2002-09-29 22:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 19:50 [PATCH] break out task_struct from sched.h Tim Schmielau
2002-09-29 20:13 ` John Levon
2002-09-29 21:00 ` Tim Schmielau
2002-09-29 21:06 ` Robert Love
2002-09-29 22:17 ` Dave Jones
2002-09-29 22:23 ` Arnaldo Carvalho de Melo [this message]
2002-09-30 7:34 ` Tim Schmielau
2002-09-30 12:17 ` Arnd Bergmann
2002-09-30 22:57 ` Tim Schmielau
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=20020929222353.GC7028@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davej@codemonkey.org.uk \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=tim@physik3.uni-rostock.de \
/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;
as well as URLs for NNTP newsgroup(s).