From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: is the weeks before -rc1 the time to really be working on -next?
Date: Wed, 15 Oct 2008 14:56:06 -0700 [thread overview]
Message-ID: <20081015145606.2af3baf1.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081015174015.GB8663@kroah.com>
On Wed, 15 Oct 2008 10:40:15 -0700
Greg KH <greg@kroah.com> wrote:
> Just wondering, I know that -next is failing right now, and is a major
> pain to produce, but that seems to be primarily due to all of the
> subsystems merging with Linus right now.
No, I'd say it's primarily due to subsystem maintainers losing
discipline and changing (or compile-time and runtime breaking) other
people's stuff. This problem appears to have become much worse since
linux-next started. I suspect Stephen is cleaning up others' trash so
they're producing more of it.
This situation has totally screwed me over, because my tree is so
dependent upon the composite everyone-else tree. And a large reason
for that dependency is not that I'm carrying patches against other
people's code - it's that they're changing (or breaking) things which
lie outside their area of responsibility.
During Stephen's absence I was forced to try to assemble a
linux-next-like tree locally and that has become much much harder than
it was before linux-next, because all those trees have gone so rampant.
On one day of last week it took me from 10:00AM until 4:00PM just to
get all the patches applied and partially compiling, despite the fact
that I had them all applied and compiling 24 hours beforehand.
> So does it even make sense to try to create a -next during the 2 weeks
> of the major merge window? It seems to just cause you a whole lot of
> work, that in the end, is mostly unecessary as all of the subsystem
> maintainers are doing the merging themselves as trees move into Linus's
> tree?
>
It's very useful to me, because my tree is based on everyone else's.
With no linux-next I'd need to either go back to pulling everyone
else's junk or I'd need to rebase on mainline.
The latter is sorely tempting. It would save me vast amounts of time
and hair-tearing. I'd base my tree on mainline and dammit I'd merge
first. So everyone who has been changing stuff which is outside their
area of responsibility and breaking other people's stuff would get to
see the consequences of their actions instead of Stephen and I bearing
the brunt of it all the time.
I fear we've reached the stage now where people are merrily merging
bright-and-shiny things into their local trees without giving much
thought at all to the consequences for others.
next prev parent reply other threads:[~2008-10-15 21:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 17:40 is the weeks before -rc1 the time to really be working on -next? Greg KH
2008-10-15 20:04 ` Geert Uytterhoeven
2008-10-15 20:30 ` Greg KH
2008-10-15 21:56 ` Andrew Morton [this message]
2008-10-15 22:08 ` Rafael J. Wysocki
2008-10-15 22:36 ` Alan Cox
2008-10-15 22:53 ` Andrew Morton
2008-10-15 23:08 ` David Miller
2008-10-15 23:41 ` Andrew Morton
2008-10-15 23:53 ` Tony Luck
2008-10-15 23:56 ` David Miller
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=20081015145606.2af3baf1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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