Re: Proposed git tree changes.

Hi,

I'm not sure how to arrange it, but a system which makes it easy for the 
open source community to contribute would be the best for everybody.

Then somebody else can maintain older kernels for you and commit updated 
patches (or maybe better: you merge commits into your tree).

Maybe it's also a good idea to add some of your most important scripts 
to the git tree, to make it easier for others to maintain tuxonice (or 
fix your scripts).

Martin


Nigel Cunningham wrote:
> Hi all.
>
> I'm considering making some changes to the way I arrange the git trees,
> partly in fulfillment of suggestions posted on this list already and
> would like your input. Proposed changes are:
> - Make one big git tree instead of separate ones for each branch
> - For each vanilla kernel version, have a upstream and a tuxonice
> branch, hence upstream-3.0, tuxonice-3.0, upstream-3.1, tuxonice-3.1,
> upstream-head, tuxonice-head and so on
> - Tags for tuxonice branches will be in the format
> tuxonice-<tuxonice-version>-for-<upstream-version>  so that there will be
> no namespace difficulties
> - At any time, only the 2 most recent upstream releases will get
> TuxOnIce updates. This will reduce the amount of testing I need to do
> before releases. Until now, I've only tended to drop old releases when
> more recent changes make backporting too much effort.
>
> If these changes sound good to people, I'll start implementing them.
> Hopefully I'll then be able to fix up my long neglected scripts and get
> regular updates and patches going again.
>
> Regards,
>
> Nigel