Which branch to use to build kmscon from your forked sources

[syntaxman]

Hello,

{ I found the instructions for compiling on your blog. Thanks! I do hope you will take up maintaining the project. :-) }

I'm disappointed that Aetf seems to have not touched the kmscon project for about two years. More to the point, I'm bummed that he hasn't applied your patches, especially the mouse support. I would like to build the project from your sources, but it looks like all the features are in separate branches. Does one of the branches function as a master branch with all the features? How should I go about this?

Is it possible you might manage the project since it seems to be orphaned?

[MacSlow]

I could fork it, although I do not want to - that has always such a hostile undertone imo - and try to stream-line the changes I put into the PRs. But I've seen an eMail from him (or somebody related to aetf's fork from upstream) regarding interest in upstream-ing my PRs. So maybe not all hope is lost :)

Currently there's quite some load from work, thus evening and weekend-coding is a bit low on my side. But that'll ease at some point. I would really like to make kmscon 'sing' on GPUs :)

I'll try to keep recent plans/work about my kmscon-efforts showing up on my blog https://blog.macslow.org