Provide tagged baseline kernel in repository?

[petterreinholdtsen]

Hi. What about providing the baseline kernel used as a starting point as a tag in the repository, to make it easier to see exactly what the caninos loucos related changes to the kernel are?

At the moment I have a hard time figuring out where the Labrador specific changes are.

[ulno]

As here is so far mainly the kernel, wouldn't it be even nicer, if there was a branch or one per driver/feature where current projects of development stages were visible? The commits are pretty big at this point.

I am pretty sure some of us wouldn't be afraid of looking at - even at unfinished - kernel code.

[petterreinholdtsen]

[Ulrich Norbisrath]

As here is so far mainly the kernel, wouldn't it be even nicer, if there was a branch or one per driver/feature where current projects of development stages were visible? The commits are pretty big at this point. I am pretty sure some of us wouldn't be afraid of looking at - even at unfinished - kernel code.

Yeah. And the current git history put me off a bit to try to figure out what is unique about the kernel, as it do not seem to prepare for merges neither from nor to the upstream kernel. To prepare for such merges, it would be better if it was be based on the upstream git repo and using a branch with the labrador specific changes.

…

-- Happy hacking Petter Reinholdtsen