rethinking patch management with GIT / topgit

[Enrico Weigelt]

Petr Baudis wrote:

> But if you need to fix up an already committed commit, you either make
> a new commit, which will break (ii), or you rebase, which will break
> anyone else working on a clone of your repository and break (i).

Yes, but is it so bad ?

Usually, you have only one person or very few ones working very
closely together per package. So that shouldnt hurt so much that
it's worth all the complexity.

Another, trivial, way is to simply add some prefix or other
formalized metadata into the commit messages, so it can be
easily parsed+handled by some little script.


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 cellphone: +49 174 7066481   email: info at metux.de   skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------