From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>,
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 23:36:07 +0100 [thread overview]
Message-ID: <20081015233607.54c1d6b8@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20081015145606.2af3baf1.akpm@linux-foundation.org>
> 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.
Its not that simple. There are areas where the tree divides don't fit the
coding divides. ttydev was horribly entwined with USB and there really
wasn't a way to break that up at the time in question. Because -next
tries to assemble all the trees based on Linus tree it can't cope with
that case well at all and in fact there was some neccessary rule bending
to make next work out where some of the ttydev work was done with ttydev
on top of other subtrees.
So at times it would be very helpful with -next to be able to do limited
tree ordering. If I could have flagged tty as requiring USB first for
example there would have been a lot less pain involved.
Alan
next prev parent reply other threads:[~2008-10-15 22:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 17:40 Greg KH
2008-10-15 20:04 ` Geert Uytterhoeven
2008-10-15 20:30 ` Greg KH
2008-10-15 21:56 ` Andrew Morton
2008-10-15 22:08 ` Rafael J. Wysocki
2008-10-15 22:36 ` Alan Cox [this message]
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=20081015233607.54c1d6b8@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=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
all inboxes | Powered by JetHome®