|
| 1 | +A short git tools survey |
| 2 | +======================== |
| 3 | + |
| 4 | + |
| 5 | +Introduction |
| 6 | +------------ |
| 7 | + |
| 8 | +Apart from git contrib/ area there are some others third-party tools |
| 9 | +you may want to look. |
| 10 | + |
| 11 | +This document presents a brief summary of each tool and the corresponding |
| 12 | +link. |
| 13 | + |
| 14 | + |
| 15 | +Alternative/Augmentative Procelains |
| 16 | +----------------------------------- |
| 17 | + |
| 18 | + - *Cogito* (http://www.kernel.org/pub/software/scm/cogito/) |
| 19 | + |
| 20 | + Cogito is a version control system layered on top of the git tree history |
| 21 | + storage system. It aims at seamless user interface and ease of use, |
| 22 | + providing generally smoother user experience than the "raw" Core GIT |
| 23 | + itself and indeed many other version control systems. |
| 24 | + |
| 25 | + |
| 26 | + - *pg* (http://www.spearce.org/category/projects/scm/pg/) |
| 27 | + |
| 28 | + pg is a shell script wrapper around GIT to help the user manage a set of |
| 29 | + patches to files. pg is somewhat like quilt or StGIT, but it does have a |
| 30 | + slightly different feature set. |
| 31 | + |
| 32 | + |
| 33 | + - *StGit* (http://www.procode.org/stgit/) |
| 34 | + |
| 35 | + Stacked GIT provides a quilt-like patch management functionality in the |
| 36 | + GIT environment. You can easily manage your patches in the scope of GIT |
| 37 | + until they get merged upstream. |
| 38 | + |
| 39 | + |
| 40 | +History Viewers |
| 41 | +--------------- |
| 42 | + |
| 43 | + - *gitk* (shipped with git-core) |
| 44 | + |
| 45 | + gitk is a simple TK GUI for browsing history of GIT repositories easily. |
| 46 | + |
| 47 | + |
| 48 | + - *gitview* (contrib/) |
| 49 | + |
| 50 | + gitview is a GTK based repository browser for git |
| 51 | + |
| 52 | + |
| 53 | + - *gitweb* (ftp://ftp.kernel.org/pub/software/scm/gitweb/) |
| 54 | + |
| 55 | + GITweb provides full-fledged web interface for GIT repositories. |
| 56 | + |
| 57 | + |
| 58 | + - *qgit* (http://digilander.libero.it/mcostalba/) |
| 59 | + |
| 60 | + QGit is a git/StGIT GUI viewer built on Qt/C++. QGit could be used |
| 61 | + to browse history and directory tree, view annotated files, commit |
| 62 | + changes cherry picking single files or applying patches. |
| 63 | + Currently it is the fastest and most feature rich among the git |
| 64 | + viewers and commit tools. |
| 65 | + |
| 66 | + |
| 67 | + |
| 68 | +Foreign SCM interface |
| 69 | +--------------------- |
| 70 | + |
| 71 | + - *git-svn* (contrib/) |
| 72 | + |
| 73 | + git-svn is a simple conduit for changesets between a single Subversion |
| 74 | + branch and git. |
| 75 | + |
| 76 | + |
| 77 | + - *quilt2git / git2quilt* (http://home-tj.org/wiki/index.php/Misc) |
| 78 | + |
| 79 | + These utilities convert patch series in a quilt repository and commit |
| 80 | + series in git back and forth. |
| 81 | + |
| 82 | + |
| 83 | +Others |
| 84 | +------ |
| 85 | + |
| 86 | + - *(h)gct* (http://www.cyd.liu.se/users/~freku045/gct/) |
| 87 | + |
| 88 | + Commit Tool or (h)gct is a GUI enabled commit tool for git and |
| 89 | + Mercurial (hg). It allows the user to view diffs, select which files |
| 90 | + to committed (or ignored / reverted) write commit messages and |
| 91 | + perform the commit itself. |
| 92 | + |
| 93 | + - *git.el* (contrib/) |
| 94 | + |
| 95 | + This is an Emacs interface for git. The user interface is modeled on |
| 96 | + pcl-cvs. It has been developed on Emacs 21 and will probably need some |
| 97 | + tweaking to work on XEmacs. |
0 commit comments