2008/8/19 Markus Hitter <[EMAIL PROTECTED]>:
>
> Am 19.08.2008 um 00:41 schrieb James Hawkins:
>
>> when the patch doesn't get committed, you should look back at it
>> and really think
>> outside the box about what could possibly be wrong with the patch.
>
> Essentially, you ask to change code on u
Am 19.08.2008 um 00:41 schrieb James Hawkins:
> when the patch doesn't get committed, you should look back at it
> and really think
> outside the box about what could possibly be wrong with the patch.
Essentially, you ask to change code on unfounded guesses (I did the
best to my knowledge in
On Mon, Aug 18, 2008 at 5:31 PM, Markus Hitter <[EMAIL PROTECTED]> wrote:
>
> Am 18.08.2008 um 19:53 schrieb James Hawkins:
>
>> Why can't a developer review his own patch? If your patch is not
>> committed, the first thing you should do is look the patch over for obvious
>> mistakes.
>
> Obviously
Am 18.08.2008 um 19:53 schrieb James Hawkins:
> Why can't a developer review his own patch? If your patch is not
> committed, the first thing you should do is look the patch over for
> obvious mistakes.
Obviously, some people here are used to receive more random diffs
instead of carefully
On Mon, Aug 18, 2008 at 7:40 AM, Markus Hitter <[EMAIL PROTECTED]> wrote:
>
> Am 18.08.2008 um 11:25 schrieb Michael Stefaniuc:
>
>> He [Alexandre] doesn't scale at replying to trivially "wrong"
>> patches but everybody
>> can reply to those and actually they should do that.
>
>
> Unfortunately, a
Am 18.08.2008 um 11:25 schrieb Michael Stefaniuc:
> He [Alexandre] doesn't scale at replying to trivially "wrong"
> patches but everybody
> can reply to those and actually they should do that.
Unfortunately, a developer can't review his patches himself and if
the patch reviewing group is to
Markus Hitter wrote:
> Am 18.08.2008 um 06:57 schrieb James Hawkins:
>
>> Also, Julliard hasn't had trouble scaling with the pace of
>> development so far.
>
> I'd be not so sure about this. So far I've filed four bugs and sent
> two patches. Bugs get little or no attention, patches obviously
Am 18.08.2008 um 06:57 schrieb James Hawkins:
> Also, Julliard hasn't had trouble scaling with the pace of
> development so far.
I'd be not so sure about this. So far I've filed four bugs and sent
two patches. Bugs get little or no attention, patches obviously
rushed through unnoticed.
Go
On Sun, Aug 17, 2008 at 11:45 PM, Hongbo Ni <[EMAIL PROTECTED]> wrote:
> "Dan Kegel" > wrote: > This guide seems rather well written: >
> http://ldn.linuxfoundation.org/how-participate-linux-community > Wine could
> probably use something similar. YES, the Wine development speed can be
> greatly im
"Dan Kegel" <[EMAIL PROTECTED]> wrote:
> This guide seems rather well written:
> http://ldn.linuxfoundation.org/how-participate-linux-community
> Wine could probably use something similar.
YES, the Wine development speed can be greatly improved if similar
development process is adepted, special
This guide seems rather well written:
http://ldn.linuxfoundation.org/how-participate-linux-community
Wine could probably use something similar.
11 matches
Mail list logo
