Proposed git tree changes.

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
-- 
Evolution (n): A hypothetical process whereby improbable
events occur with alarming frequency, order arises from chaos, and
no one is given credit.