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.30.2101 +0200]:
> > > 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 ?
> 
> At least in Debian, we have to support multiple releases.

Okay, and what exactly is the problem w/ my suggested workflow ?

Actually, I have to support lots of versions for different distros,
including special inhouse patches (eg. redirecting mysql connections
within client library, for some large mass hoster). My branch hierachy
approach (w/ frequent rebasing) works pretty well here.


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/
---------------------------------------------------------------------