rethinking patch management with GIT / topgit

[Petr Baudis]

On Wed, Mar 24, 2010 at 04:36:14PM +0100, Enrico Weigelt wrote:
> Petr Baudis wrote:
> 
> > But what if you need to change one of the already committed patches?
> 
> Simply add a new commit ?
> Remember: we're not thinking in "patches" here (forget that term
> at all ! ;-), but in (distro-specific) maintenance-_branches_.
> 
> That's a totally different approach. A process manager would say,
> we're adding a new role: a QM-developer. (the one who's responsible
> for making QM'ed releases out of the often messed up upstream).

Ok, but then you need to acknowledge that the properties I mentioned are
something you are not interested in. And if you think others should
follow suite, it would be good to explain _why_ they aren't desirable
enough.

-- 
				Petr "Pasky" Baudis
http://pasky.or.cz/ | "Ars longa, vita brevis." -- Hippocrates