Aleksey Bragin wrote:
"It should try every revision, otherwise there is no use from it at all. And automerge from trunk to stable branch is not possible, because patches usually depend on each other."
Sorry,i explained myself wrong, i was not talking about automerging, or using the "stable branch" to send patches. No, patches would be still sent to the unstable branch, and no "automerging will be used", it will be just overwriting.
The process i imagine like this:
-Unestable not working. -Recent Stable working (1 day old). -You dont have the skill to fix unstable. -You download stable, work in your computer over stable. -Send changes to unstable (then things become interesting). -Check the files you are have touched. If no other person have touched them since the stable (1 day old) was made you can send your patches, if someone have touched, you cant and have to wait till the stable revision is updated. -Once unstable boot again, stable is override by the unstable, and now named stable.
This would alow people working, maybe in the control panel, with little kernel or booting code knowledge, keep working without having to stop developing for dificult bugs in the kernel.
What do you thing? Maybe is a crazy idea cause i dont know about the inners of SVN.
______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com
-
Lucio Diaz