No objections so far.

> I'd like to completely merge 2.16 into trunk and remove 2.16 altogether.
> 
> This will also mean the upcoming genericno.sesam.no-2.16.1 release will
> instead be a genericno.sesam.no-2.17. This should greatly simplified the
> mess the has occurred with the different 2.16 branches.

I will go ahead with this directly before the upcoming feature freeze.
Steps i will take:
 1) move 2.17 issues to 2.18
 2) move 2.16.2 issues to 2.18.1
 3) move 2.16.1 issues to 2.18
 4) merge 2.16 changes into 2.17
 5) Update genericno.sesam.no to use sesat-kernel 2.17 and to be 2.17
 6) remove sesat.no/svn/sesat-kernel/branches/2.16
 7) recreate sesat.no/svn/sesat-kernel/branches/2.16 from sesat.no/svn/
sesat-kernel/branches/2.16.0

I'll send another mail when this has been done!

~mck

-- 
"The turtle only makes progress when it's neck is stuck out" Rollo May
| www.semb.wever.org | www.sesat.no | www.sesam.no |

_______________________________________________
Kernel-development mailing list
[email protected]
http://sesat.no/mailman/listinfo/kernel-development

Reply via email to