From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: Please route new work through -mm tree?
Date: Wed, 29 Sep 2004 13:19:47 -0700 [thread overview]
Message-ID: <20040929131947.03c3e9e5.davem@redhat.com> (raw)
In-Reply-To: <1096481023.8636.7.camel@localhost.localdomain>
On Wed, 29 Sep 2004 11:03:43 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> There is lots of stuff going on that has a potential to make things less
> stable. How about routing any future TCP, fib, statistics, stuff through
> Andrew's tree and not directly to Linus. That way we have some buffer
> and can stablize some more. Alternatively, Dave you could publize your
> staging area some more.
I'm not changing how I do things because:
1) Putting the net stuff into -mm makes debugging of networking
changes harder, as -mm has a ton of experimental stuff in it
as well. -mm frequently makes machines unbootable, and particularly
this is felt on non-x86 platforms such as sparc64 which is where
I do all of my work.
2) I am more than happy to post the location of my net-2.6 tree
but last time I used this actively (whilst Linus was away for
2 weeks) the IBM folks complained that this gave them
too many trees to work from.
Furthermore, I've never put any change into my tree that I didn't
think was ready for upstream. When I post something here before
pushing to Linus, that's the chance for folks to test things out.
prev parent reply other threads:[~2004-09-29 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 18:03 Please route new work through -mm tree? Stephen Hemminger
2004-09-29 18:13 ` Nivedita Singhvi
2004-09-29 18:23 ` Marcos D. Marado Torres
2004-09-29 20:22 ` David S. Miller
2004-09-29 20:58 ` Nivedita Singhvi
2004-09-29 21:24 ` David S. Miller
2004-09-29 21:37 ` Jeff Garzik
2004-09-29 21:44 ` David S. Miller
2004-09-29 22:30 ` Jeff Garzik
2004-09-29 21:12 ` Gerrit Huizenga
2004-09-29 20:19 ` David S. Miller [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=20040929131947.03c3e9e5.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).