rethinking patch management with GIT / topgit

[Manoj Srivastava]

On Sun, Mar 28 2010, Enrico Weigelt wrote:

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

        Yes.

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

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

        manoj

-- 
Once a word has been allowed to escape, it cannot be recalled. Quintus
Horatius Flaccus (Horace)
Manoj Srivastava <srivasta at acm.org> <http://www.golden-gryphon.com/>  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C