Re: [PATCH 2/2] Move sequencer to builtin

On Sun, Jun 9, 2013 at 2:54 PM, Ramkumar Ramachandra <artagnon@gmail.com> wrote:

This is a good example of an evolving discussion. René Scharfe has accepted that the API indeed needs work. How exactly it's going to be fixed is not entirely clear, but at least there's a patch that essentially tackles what I tried to tackle.

So it's good for the users.

This also evolved rather nicely, since there is discussion about exactly how the signals should be presented to Windows users, because it's clear currently most of the codes only work in Linux.

Again, users benefit from this.

Unfortunately nobody took the charge on this ones, so we will remain forever in a non-ideal situation.

It's not my fault though. I sent the patch that fixes the problem, and there's only so much I can do.

Not that it matters much, because the important patches were applied.

But what does this have to do with anything? How are you helping the Git project by bringing this up? How does this help our users?