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

PrevNext  Index
DateMon, 04 Jun 2012 17:32:26 +0100
From Harry van Haaren <[hidden] at gmail dot com>
ToPaul Davis <[hidden] at linuxaudiosystems dot com>
CcJACK <[hidden] at lists dot jackaudio dot org>
In-Reply-ToPaul Davis Re: [Jack-Devel] how you can love JACK back
Follow-UpPaul Davis Re: [Jack-Devel] how you can love JACK back
On Mon, Jun 4, 2012 at 5:16 PM, Paul Davis <[hidden]>wrote:

> the initial goal is to be *able* to ask these qestions.
>
> once we can ask them easily and across the entire API, the next goal is to
> actually *ask* them :)
>

Ok: but what's the point in looking at everything twice??

For the sake of easy documentation like above I feel confident enough to
know what to do.

When things get more complicated, perhaps I can post to list? There's some
threading comments added to Jack2 headers and I don't know exactly what to
do with them.


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
PrevNext  Index

1338827575.24358_0.ltw:2,a <CAKudYbOQ_eUOHqAPfeL_WFqgfuV5_zyeUX=OkvwtgrrzqiKTVA at mail dot gmail dot com>