-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan Luebbe wrote: > On Sun, 2008-10-05 at 10:23 +0100, Andy Green wrote: >> I wrote a pretty comprehensive dump of my stgit and git "knowledge" some >> months ago, although I still feel I don't know a lot about git I have >> since found the data in here is about 90% of what you need to do a >> really great job working with an upstream and branches and rebasing >> really easily (allowing that you still have to resolve most conflicts >> manually anyway). > > Maybe we should use topgit instead of stgit: > > http://repo.or.cz/w/topgit.git?a=blob_plain;f=README;hb=HEAD > >>From the README: > > TopGit aims to make handling of large amount of interdependent topic
Thanks for the pointer, it's good to know there's something to look at if stgit starts getting cramped. I'm using stgit as a purely local patch stack thing, it's always just git in the repo. So nobody has to use stgit, nor will it get in their way if they don't want to: it's just I found it a really empowering way. If anyone tries topgit I'm sure I won't be the only person interested to read how they got on, it's true that stgit takes a dump on the branch history every time you perform stack operations. - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjoz2MACgkQOjLpvpq7dMrJ3ACdHlX2ggx6be7YX8V2YhpOuZqE fgYAn0R+PilAjS8NRJznITctST2Ffg1Z =d9YH -----END PGP SIGNATURE-----
