summaryrefslogtreecommitdiff
path: root/diffcore-rename.c
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2007-06-21 04:51:00 (GMT)
committerJunio C Hamano <gitster@pobox.com>2007-06-23 05:32:32 (GMT)
commit37cd4f7e820da82e5731c06b7ebf83963d796e5e (patch)
tree8233136378d5c9e815115ea5a4086840727e94fa /diffcore-rename.c
parent47ee8ed292f14e819d8e449a56c2de02d1892483 (diff)
downloadgit-37cd4f7e820da82e5731c06b7ebf83963d796e5e.zip
git-37cd4f7e820da82e5731c06b7ebf83963d796e5e.tar.gz
git-37cd4f7e820da82e5731c06b7ebf83963d796e5e.tar.bz2
Document git-gui, git-citool as mainporcelain manual pages
Jakub Narebski pointed out that the git-gui blame viewer is not a widely known feature, but is incredibly useful. Part of the issue is advertising. Up until now we haven't even referenced git-gui from within the core Git manual pages, mostly because I just wasn't sure how I wanted to supply git-gui documentation to end-users, or how that documentation should integrate with the core Git documentation. Based upon Jakub's comment that many users may not even know that the gui is available in a stock Git distribution I'm offering up two basic manual pages: git-citool and git-gui. These should offer enough of a starting point for users to identify that the gui exists, and how to start it. Future releases of git-gui may contain their own documentation system available from within a running git-gui. But not today. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'diffcore-rename.c')
0 files changed, 0 insertions, 0 deletions