Re: [Gnash-dev] Another revno.h silly commit by rob

[Rob Savoye]

On 12/09/10 10:38, strk wrote:

> The commit log sounds good. Only problem is that the old code was 
> already doin that (only updating revno.h if something changed) while 
> the new code forces rebuilding:

  The new code only rebuilds revno.h after a revision change, ie... a
git commit or git pull.

> Of course he also removed the use of conditionals to check existance
> of git:
        ...
> I guess "it was better before"

  Better is a matter of opinion... When we can't decide, it's up to me.
Sorry, but that's the way it is. Otherwise we deadlock...

>  I hope Rob will learn to work in a team.

  I'm not the one reverting changes. Reverting changes is not the proper
behavior for a team member. Reverting changes is like stomping on
somebodies toes. I am completely part of a team, I fixed a number of
bugs yesterday for several other people. That's what a team, does, is
works together... You have this amazing ability to accuse others of the
same behaviors you exhibit.

  Course now on top of revno.h breakage, I have to deal with the new
input device breakage. Since I'm working on the Framebuffer code right
now, this is a problem... I am willing to give any developer the benefit
of doubt on things like this, but I expect the same courtesy. Your bad
attitude and personal attacks are counter productive.

  I thought that was what I was doing when I *modified* the revno.h
target, to fix your changes to work the way they need to. Otherwise you
shut down my whole build farm. That seemed important enough to go fix
the revno.h target.

  Considering I wrote that Makefile.am, including the revno.h target,
and all the packaging code, have maintained it since it was added, I
think I have the ability to make the right changes to that makefile target.

  Let's drop this thread and go back to work *together*... I'm done
arguing about it.

        - rob -