From: Martin Costabel <costabel@wanadoo.fr>
To: Tom Rini <trini@disparity.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Is the vger 2.2 kernel branch dead
Date: Tue, 20 Jul 1999 21:46:41 +0200 [thread overview]
Message-ID: <3794D221.149CF3FC@wanadoo.fr> (raw)
In-Reply-To: Pine.BSF.3.96.990720135224.50420R-100000@silver.teardrop.net
Tom Rini wrote:
>
> On Tue, 20 Jul 1999, Neil Piercy wrote:
>
> > From: Tom Rini <trini@disparity.net>
> >
> > > On Mon, 19 Jul 1999, Johnnie Peters wrote:
> > >
> > > Try putting 'em vs 2.3.x. I think right now the push is to fix all the
> > > little annoyances/problems that we're stuck w/ in 2.2.x and move forward
> > > in 2.3.x. Then backport things later on.
> >
> > I thought 2.2.x was meant to be the stable branch and 2.3.x the dev ? It
> > seems strange to back-port fixes to known bugs in the stable branch from a
> > dev branch which is frequently broken - or do I misunderstand ? Stable
> > doesnt equal frozen in my book.
>
> 2.2.x is for obvious and correct stuff, important fixes and the like.
> Some of the stuff no doubt belongs in 2.2.x. Other things I've seen go
> past (Hotswap PCI) is most definatly a 2.3.x thing (IMHO) and might need
> some work to be accepted by linus (as hotswap is a generic thing, but i
> didn't look over that patch very well). Of course another problem is
> making sure Cort or Paul actually sees the patch and doesn't accidently
> just delete it. I know Cort gave some people who asked accounts on
> linuxppc.cs.nmt.edu for patches, and I think there's a place anyone can
> upload...
Is anyone in the PPC camp actually following the vger 2.3.x branch? I am
asking because since almost a month this branch hasn't compiled on my
ppc any more, due to some obvious bugs. Maybe it is better to wait until
the dust from that page-cache adventure has settled?
--
Martin
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-07-20 19:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-19 13:39 Is the vger 2.2 kernel branch dead VALETTE Eric
1999-07-19 20:39 ` Matt Porter
1999-07-19 21:07 ` Hartmut Koptein
1999-07-19 21:41 ` cdrecord (Re: Is the vger 2.2 kernel branch dead) Brad Midgley
1999-07-19 21:52 ` Is the vger 2.2 kernel branch dead Johnnie Peters
1999-07-19 22:47 ` Tom Rini
1999-07-20 17:40 ` Neil Piercy
1999-07-20 17:56 ` Tom Rini
1999-07-20 19:46 ` Martin Costabel [this message]
1999-07-21 16:20 ` Matt Porter
1999-07-21 19:47 ` Johnnie Peters
1999-07-22 7:57 ` VALETTE Eric
1999-07-22 8:14 ` Geert Uytterhoeven
1999-07-22 8:41 ` VALETTE Eric
1999-07-22 15:01 ` Matt Porter
1999-07-22 15:53 ` VALETTE Eric
1999-07-22 16:54 ` Unresolved symbols ian reinhart geiser (ADMIN)
1999-07-22 17:15 ` Daniel Jacobowitz
1999-07-22 17:23 ` ian reinhart geiser (ADMIN)
1999-07-24 8:46 ` Franz Sirl
1999-07-23 2:41 ` Is the vger 2.2 kernel branch dead Paul Mackerras
1999-07-23 7:48 ` VALETTE Eric
1999-07-20 7:57 ` VALETTE Eric
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=3794D221.149CF3FC@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@disparity.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;
as well as URLs for NNTP newsgroup(s).