Hello everyone,
I think it's time that we discuss how / when to merge the SoC
contributions. Can each maintainer give their current status?
When it comes to vis: The code seems to work pretty well on Linux and
OSX, some roughness that I think we can polish away when we have more
people using it.
On 9/24/07, Tobias Rundström <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> I think it's time that we discuss how / when to merge the SoC
> contributions. Can each maintainer give their current status?
How about a little summary of the summer's work and where we stand on
merge readiness from ea
Tobias Rundström wrote:
> Hello everyone,
>
> I think it's time that we discuss how / when to merge the SoC
> contributions. Can each maintainer give their current status?
GenIPC is unfortunately not ready for merge.
anders
--
___
Xmms2-devel mail
Dan Chokola wrote:
>> I think it's time that we discuss how / when to merge the SoC
>> contributions. Can each maintainer give their current status?
>
> How about a little summary of the summer's work and where we stand on
> merge readiness from each mentor?
Yeah, how about each mentor give thei
On 9/24/07, Anders Waldenborg <[EMAIL PROTECTED]> wrote:
> Dan Chokola wrote:
> >> I would like to do DrKelso before the end of oct and then merge all
> >> mergable socs into -devel.
> >
> > How about merging them into another branch somewhere? Leveraging Git
> > here means we can merge in a separa
On 9/24/07, Tobias Rundström xmms.org> wrote:
> Can each maintainer give their current status?
Service clients are in a working state. More testing is needed to
find possible bugs, but it's feature-complete.
However I'd like people to review the API and comment on it. We've
struggled a few tim
On Tue, Sep 25, 2007 at 11:23:10AM +0900, Sébastien Cevey wrote:
> rafl, any comment about that, since you already had a look at them,
> earlier and yesterday?
There are some functions which could have a better and more intuitive
name like xmmsc_service_method_attribute_get.
Also the xmmsc_servic
