Re: [Jack-Devel] how you can love JACK back

On Mon, Jun 4, 2012 at 12:32 PM, Harry van Haaren <[hidden]>wrote:

>
> Workflow suggestion:
> -I'll work away, when things are obvious (like adding @deprecated tags
> etc) I'll just do it
>
-When things are hard, I'll keep them in a seperate commit in git, and post
> a link to the list pointing to that commit's diff, and we can discuss the
> issue using Github comment features?
>
> Could this be a good workflow? -Harry
>

it could be. the goal is to end up with a single set of headers that will
be accepted as *the* headers for JACK, definitively defining the API, and
shared by any implementation. this means that if you make any changes that
are even a teensy-weensy bit controversial, it will make the later adoption
a bit harder. other than that, go for it!

1338827725.24404_0.ltw:2,a <CAFa_cKmtXWJkcyO5q9q3Ck=sJ7rsoWq7qkXcSLiVNTD=S3B0mQ at mail dot gmail dot com>