From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken
Date: Wed, 18 Jun 2003 17:27:09 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.55L.0306181719580.23915@freak.distro.conectiva> (raw)
In-Reply-To: <20030617235838.GA2677@werewolf.able.es>
On Wed, 18 Jun 2003, J.A. Magallon wrote:
>
> On 06.18, Marcelo Tosatti wrote:
> >
> >
> > On Wed, 11 Jun 2003, Eric Valette wrote:
> >
> > > Marcelo Tosati wrote:
> > >
> > > >The main reason I didnt want to merge it was due to its size. Its just
> > > >too big.
> > >
> > > >> Please stop leading me along. Will you EVER merge it?
> > >
> > > >Yes, I want to, and will merge it. In 2.4.23-pre.
> > >
> > > This kind of mails and sentence makes you lost your credibility :
> > > 1) You said that ACPI will be merged in 2.4.22-pre,
> > > 2) For many people ACPI (and aic7xxx) is top priority for 2.4 kernel
> > > (see various post including alan). The reason being that most laptop are
> > > unusable nowadays without ACPI,
> > > 3) You do not explicitely says what you plan for 2.4.22...
> >
> > My plan for 2.4.22 is:
> >
> > - Include the new aic7xxx driver.
> > - Include ACPI. (I now realized its importance). Already discussing with
> > Andrew the best way to do it.
> > - Fix the latency/interactivity problems (Chris, Nick and Andrea working
> > on that)
> > - Merge obviously correct -aa VM patches.
> >
> > Those are the most important things that are needed now, I think.
> >
>
> Would you accept small canges like -march (gcc_check) for x86 ?
I'm not aware of this patch. I might well accecpt it.
Please submit it with a good explanation and I will consider it.
next prev parent reply other threads:[~2003-06-18 20:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 23:40 Eric Valette
2003-06-11 21:15 ` Adrian Bunk
2003-06-12 11:47 ` Eric Valette
2003-06-12 14:05 ` Stephan von Krawczynski
2003-06-12 16:32 ` Eric Valette
2003-06-17 23:25 ` Marcelo Tosatti
2003-06-17 23:58 ` J.A. Magallon
2003-06-18 20:27 ` Marcelo Tosatti [this message]
2003-06-18 5:15 ` Anders Karlsson
2003-06-18 16:55 ` Bill Nottingham
2003-06-18 9:04 ` Eric Valette
-- strict thread matches above, loose matches on Subject: below --
2003-06-09 23:27 Grover, Andrew
2003-06-09 22:38 Margit Schubert-While
2003-06-10 0:08 ` Marcelo Tosatti
2003-06-09 21:47 Margit Schubert-While
2003-06-09 21:21 Grover, Andrew
2003-06-09 21:24 ` Grzegorz Jaskiewicz
2003-06-09 22:03 ` Marcelo Tosatti
2003-06-10 0:44 ` Alan Cox
2003-06-10 11:05 ` Torben Mathiasen
2003-06-10 15:14 ` Stephan von Krawczynski
2003-06-09 21:07 Margit Schubert-While
2003-06-04 20:49 Grover, Andrew
2003-06-09 20:32 ` 2.4.22 timeline was " Marcelo Tosatti
2003-06-10 0:47 ` Alan Cox
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=Pine.LNX.4.55L.0306181719580.23915@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®