| commit | 16dd62ac4de10c9ae27d29bb1c906ad97ac8908f | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 18 May 2008 17:08:17 +0000 (18 13:08 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 20 May 2008 19:44:46 +0000 (20 15:44 -0400) | ||
| tree | 26a475c0a74f51872513993c41e8e15286df9fa5 | treesnapshot (tar.gz zip) |
| parent | 76bb40cde0e15e8d0e8493abb0bd18a5d6386ad7 | commitdiff |
git-gui: Add a --trace command line option
Often new Git users want to know what commands git-gui uses to make
changes, so they can learn the command line interface by mimicking
what git-gui does in response to GUI actions. Showing the direct
commands being executed is easy enough to implement but this is of
little value to end-users because git-gui frequently directly calls
plumbing, not porcelain.
Since the code is already written and tested, its fairly harmless
to include. It may not help a new end-user, but it can help with
debugging git-gui or reverse-engineering its logic to further make
changes to it or implement another GUI for Git.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Often new Git users want to know what commands git-gui uses to make
changes, so they can learn the command line interface by mimicking
what git-gui does in response to GUI actions. Showing the direct
commands being executed is easy enough to implement but this is of
little value to end-users because git-gui frequently directly calls
plumbing, not porcelain.
Since the code is already written and tested, its fairly harmless
to include. It may not help a new end-user, but it can help with
debugging git-gui or reverse-engineering its logic to further make
changes to it or implement another GUI for Git.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| git-gui.sh | diffblobblamehistory |