From: Randy Dunlap <randy.dunlap@oracle•com>
To: Geert Uytterhoeven <geert@linux-m68k•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Linus Torvalds <torvalds@linux-foundation•org>,
Andrew Morton <akpm@linux-foundation•org>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: circumvention and ignorance (was: Re: linux-next: Tree for July 22)
Date: Tue, 22 Jul 2008 20:10:05 -0700 [thread overview]
Message-ID: <20080722201005.2d1081f5.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0807230140000.28765@anakin>
On Wed, 23 Jul 2008 01:49:30 +0200 (CEST) Geert Uytterhoeven wrote:
> Hi all,
>
> Looking at today's http://kisskb.ellerman.id.au/kisskb/matrix/, there's
> plenty of red, and not only in the linux-next division :-(
>
> On Tue, 22 Jul 2008, Stephen Rothwell wrote:
> > We are up to 105 trees (counting Linus' and 14 trees of patches pending for
> > Linus' tree), more are welcome (even if they are currently empty).
> > Thanks to those who have contributed, and to those who haven't, please do.
>
> We still see regular merging of trivially breaking patches that
> apparently never have been in linux-next...
>
> > The ttydev tree was partially merged upstream and gained so many
> > conflicts that I have temporarily dropped it.
>
> Worse, we're seeing things getting merged that have been known-broken in
> several linux-next incarnations during the last few weeks...
>
> Now we have such a great thing like linux-next (thanks, Stephen! You
> saved my day a lot lately), perhaps we should start making full use of
> it?
E.g., we don't seem to have a good method of moving build fixes into their
appropriate tree/patchset. Or maybe it's just that we can't get them
noticed by the appropriate people.
---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/
prev parent reply other threads:[~2008-07-23 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 8:40 linux-next: Tree for July 22 Stephen Rothwell
2008-07-22 23:49 ` linux-next: circumvention and ignorance (was: Re: linux-next: Tree for July 22) Geert Uytterhoeven
2008-07-23 3:10 ` Randy Dunlap [this message]
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=20080722201005.2d1081f5.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=geert@linux-m68k$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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