From: Ralf Baechle <ralf@linux-mips.org>
To: Rik van Riel <riel@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Chuck Wolber <chuckw@quantumlinux.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: Development Model
Date: Wed, 20 Apr 2005 21:22:22 +0100 [thread overview]
Message-ID: <20050420202222.GA4551@linux-mips.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0504191522140.18066@chimarrao.boston.redhat.com>
On Tue, Apr 19, 2005 at 03:24:00PM -0400, Rik van Riel wrote:
> The current development model seems to go much smoother than
> anything I've seen before.
It violates conventional wisdom and that psychological thing is the lion
share of why some people feel uneasy about it.
Dealing with the parallel work on 2.4 and 2.5 was very much like the
attempt of drinking from a firehose, so I'm very happy only having only to
deal with 2.6, not 2.7 also.
Ralf
next prev parent reply other threads:[~2005-04-21 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 5:31 Development Model Chuck Wolber
2005-04-19 14:20 ` bert hubert
2005-04-19 14:50 ` Arjan van de Ven
2005-04-19 19:24 ` Rik van Riel
2005-04-20 20:22 ` Ralf Baechle [this message]
2005-04-19 20:26 ` Florian Weimer
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=20050420202222.GA4551@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=arjan@infradead.org \
--cc=chuckw@quantumlinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=torvalds@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