[PATCH] Add trim support to qapitrace GUI app

[José Fonseca]

On Fri, Mar 16, 2012 at 7:10 PM, Carl Worth <cworth at cworth.org> wrote:
> I won't express any opinion on how much functionality should be
> implemented before the changes are accepted upstream. That's not my
> call.

Actually, I'd like to say a few words on this matter.

Because git makes it so easy to fork, I'm seeing proliferation of
incomplete feature branches, many of which my own. This is
inefficient: branches quickly become outdated, and hard to merge,
different people end up doing similar work twice. Furthermore, I don't
like the prospects of different groups starting to use forked versions
of apitrace.

So I'm starting to hack down on this. I've moved the todo list to the
wiki https://github.com/apitrace/apitrace/wiki/ToDo and ensure that
all pending patches/branches are listed there, and will integrate
things

As a long as a feature does not cause regressions, it's not
implemented in a way that will hinder further development, or so
incomplete that's likely to cause many bug reports, I'd like to get it
into master sooner rather than later, doing the cleanups myself if
necessary.

Dan patches too. Some cleanups might be in order, but one way or the
other I'd like to get this stuff in, either deferring the cleanups or
doing them myself.

Jose