rethinking patch management with GIT / topgit

[Enrico Weigelt]

* martin f krafft <madduck at debian.org> schrieb:
> also sprach Enrico Weigelt <weigelt at metux.de> [2010.03.24.1636 +0100]:
> > > But what if you need to change one of the already committed patches?
> > 
> > Simply add a new commit ?
> 
> To every maintenance branch, without the possibility to track the
> commit?

Why do you have so many different maintenance branches for the
same packages so you need some automatic tracking ?

Why do you not get along with an clear producer-consumer 
hierachy ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service - http://www.metux.de/
---------------------------------------------------------------------
 Please visit the OpenSource QM Taskforce:
 	http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
	http://patches.metux.de/
---------------------------------------------------------------------