rethinking patch management with GIT / topgit

[Petr Baudis]

On Sun, Mar 28, 2010 at 09:40:45AM -0700, Manoj Srivastava wrote:
> On Sun, Mar 28 2010, Enrico Weigelt wrote:
> > 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.
> 
>         False assumption: it might be the case for you that you work in
>  a small team, and know all people who base their work on yours, and
>  perhaps you package for a leaf distribution.
> 
>         None of those hold in my case.

My original motivation for TopGit development was that I actually was
the _only_ developer, but I needed to maintain and develop in multiple
clones in a sensible way.

Maybe you are happy doing things your way, but I'm trying to explain why
many people aren't.

> > 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.
> 
>         Sounds like a kludge.

...and I'm not actually able to fill in the gaps.

				Petr "Pasky" Baudis