> Could you please add info about teamGit to the git wiki pagehttp://git.or.cz/gitwiki/InterfacesFrontendsAndTools? I think > just below now defunct and unmaintained KGit (or just above) would > be best. Will do ASAP > P.S. How it differs from othe Git GUIs, like gitk+git-gui, qgit > or git-cola?It differs from 1. gitk and git-gui : its not as ugly :p, well actually neither of them fulfilled speed requirements on my 'not so old' but 'ancient by computer standards' p4 laptop. 2. qgit4 : actually its not very different except that i don't find interface of qgit too friendly. Neway i would have used qgit instead if it was at the stage its now two years back. i also tried to base my code off qgit's plumbing unfortunately it wasn't easy to rip it. I didn't like the complicated unreadable typical c++ code design so chose not to participate in there. (to make things clear qgit is excellent, and wonderfully coded. Marc has done real good job of using c++ to its fullest and this is not a comment on his coding capabilities. Its only that i am just too poor a c++ developer and consider c++ too confusing for active contirbution in core design by others.) So one of the aims i have in teamGit is to keep it as clean and simple as possible (not easy goal i must add and i might already be off). 3. git-cola: i hate scirpting used as mainstay applications. Besides all of the above teamGit differes drastically in its end roadmap. It will ultimately be complete project management tool. A developer should be able to completely manage his coding activities from inside teamGit, plus a team collaberation added as an advantage. But these are reallllyyyyyy lloooonnngg term goals, if it ever gets there. Thanks, BAIN -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
