gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnash-commit] [SCM] Gnash branch, hwaccel, updated. release_0_8_9_f


From: Rob Savoye
Subject: Re: [Gnash-commit] [SCM] Gnash branch, hwaccel, updated. release_0_8_9_final-1079-ga77b2d1
Date: Tue, 09 Aug 2011 07:44:54 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc13 Lightning/1.0b2 Thunderbird/3.1.10

On 08/08/11 23:22, Benjamin Wolsey wrote:

> Knowingly introducing bugs for even 1% of users still isn't suitable for
> a stable branch! And whether I'm directly "affected" by these changes or
> not is also irrelevant: does it mean I shouldn't care about the quality
> of code added to Gnash? We all still have to maintain it once it's
> there.

  You are still getting upset about something that hasn't happened yet.
I care deeply about the quality and stability, even though it's obvious
you and I differ on what we consider clean and stable. My feeling on
this is pretty simple. I started this project and plan to continue
working on Gnash. If you can't tolerate my coding style, etc... then you
need to fork Gnash into your own project where you don't have to deal
with me and my code ever again.

  It's that simple. Either get used to me adding code to my own project,
or start your own. I will *not* allow you to force me off my own project
for just cause you have a bad attitude. I worked on this project for
many years before you ever joined this team. This is *your* decision
point, you can chill out and stop trying to prevent me from adding code
to my own project, or start your own.

  Considering our lack of resources, I think a Gnash fork would be a big
mistake. Continuing the endless flame war is also a big mistake. Some of
us are trying hard to push Gnash forward, and that's easier without you
nit-picking everything to death.

        - rob -



reply via email to

[Prev in Thread] Current Thread [Next in Thread]