Hi -
> My concern is that only "get my line of code merged" is seen as "the
> ultimate thing". It's more than that. Linux is about collaboration [...]
Unfortunately, this spirit of collaboration sometimes gets lost in
practice when feedback is asymmetric, obnoxious, or absent.
- FChE
-
To
Arjan van de Ven <[EMAIL PROTECTED]> writes:
> [...]
> It does not matter [whose] code gets merged.
> What matters is that the problem gets solved and that the Linux kernel
> innovates forward.
> [...]
This attitude has risks over the long term, if outsiders with fresh
ideas are discouraged.
On Thu, 2007-08-02 at 16:03 -0400, Frank Ch. Eigler wrote:
> Arjan van de Ven <[EMAIL PROTECTED]> writes:
>
> > [...]
> > It does not matter [whose] code gets merged.
> > What matters is that the problem gets solved and that the Linux kernel
> > innovates forward.
> > [...]
>
> This attitude has
On Wed, Aug 01, 2007 at 12:05:01AM -0700, Arjan van de Ven wrote:
> I've had several cases myself where I spent quite some time solving a
> problem, just to get some random remark from someone smart on lkml
> saying "if you had done you would have had simple and superior solution>". Was I pissed
On Wed, Aug 01, 2007 at 12:05:01AM -0700, Arjan van de Ven wrote:
I've had several cases myself where I spent quite some time solving a
problem, just to get some random remark from someone smart on lkml
saying if you had done this simple thing you would have had this
simple and superior
Arjan van de Ven [EMAIL PROTECTED] writes:
[...]
It does not matter [whose] code gets merged.
What matters is that the problem gets solved and that the Linux kernel
innovates forward.
[...]
This attitude has risks over the long term, if outsiders with fresh
ideas are discouraged. Risking
On Thu, 2007-08-02 at 16:03 -0400, Frank Ch. Eigler wrote:
Arjan van de Ven [EMAIL PROTECTED] writes:
[...]
It does not matter [whose] code gets merged.
What matters is that the problem gets solved and that the Linux kernel
innovates forward.
[...]
This attitude has risks over the
Hi -
My concern is that only get my line of code merged is seen as the
ultimate thing. It's more than that. Linux is about collaboration [...]
Unfortunately, this spirit of collaboration sometimes gets lost in
practice when feedback is asymmetric, obnoxious, or absent.
- FChE
-
To unsubscribe
On Wed, 2007-08-01 at 11:40 -0700, Hua Zhong wrote:
> > > And, from a standpoint of ONGOING, long-term innovation: what matters
> > > is that brilliant, new ideas get rewarded one way or another.
> >
> > and in this case, the reward is that the idea got used and credit was
> > given
>
> You
> > And, from a standpoint of ONGOING, long-term innovation: what matters
> > is that brilliant, new ideas get rewarded one way or another.
>
> and in this case, the reward is that the idea got used and credit was
> given
You mean, when Ingo announced CFS he mentioned Con's name?
I really
On Wed, 2007-08-01 at 10:14 +0200, [EMAIL PROTECTED] wrote:
> On 8/1/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > Let me repeat the key message:
> >
> > It does not matter who's code gets merged.
> > It does not matter who's code gets merged.
> > It does not matter who's code gets merged.
>
On 8/1/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> Let me repeat the key message:
>
> It does not matter who's code gets merged.
> It does not matter who's code gets merged.
> It does not matter who's code gets merged.
> It does not matter who's code gets merged.
>
> What matters is that the
Arjan van de Ven wrote:
Let me repeat the key message:
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
What matters is that the problem gets solved and that the Linux
On Tue, 2007-07-31 at 23:16 -0700, Hua Zhong wrote:
> > Did Ingo have the obligation to improve Con's work? Definitely not.
> > Did Con have a right to get Ingo's improvements or
> > suggestions? Definitely not.
>
> Yes, and that's where the inequality is.
>
> Unless the maintainer does a really
On Tue, 2007-07-31 at 23:16 -0700, Hua Zhong wrote:
Did Ingo have the obligation to improve Con's work? Definitely not.
Did Con have a right to get Ingo's improvements or
suggestions? Definitely not.
Yes, and that's where the inequality is.
Unless the maintainer does a really bad job
Arjan van de Ven wrote:
Let me repeat the key message:
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
What matters is that the problem gets solved and that the Linux
On 8/1/07, Arjan van de Ven [EMAIL PROTECTED] wrote:
Let me repeat the key message:
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
What matters is that the problem
On Wed, 2007-08-01 at 10:14 +0200, [EMAIL PROTECTED] wrote:
On 8/1/07, Arjan van de Ven [EMAIL PROTECTED] wrote:
Let me repeat the key message:
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not matter who's code gets merged.
It does not
And, from a standpoint of ONGOING, long-term innovation: what matters
is that brilliant, new ideas get rewarded one way or another.
and in this case, the reward is that the idea got used and credit was
given
You mean, when Ingo announced CFS he mentioned Con's name?
I really doubt
On Wed, 2007-08-01 at 11:40 -0700, Hua Zhong wrote:
And, from a standpoint of ONGOING, long-term innovation: what matters
is that brilliant, new ideas get rewarded one way or another.
and in this case, the reward is that the idea got used and credit was
given
You mean, when
20 matches
Mail list logo
