summaryrefslogtreecommitdiff
path: root/t/t9134-git-svn-ignore-paths.sh
diff options
context:
space:
mode:
authorLibravatar Jonathan Nieder <jrnieder@gmail.com>2010-11-10 13:00:48 -0600
committerLibravatar Junio C Hamano <gitster@pobox.com>2010-11-11 10:57:16 -0800
commit6f02a5a33a3983597992e94c7b826021acc8a9d9 (patch)
treebdf0b0484f629fbacada6af9b6a923d22e367306 /t/t9134-git-svn-ignore-paths.sh
parentDocumentation: split gitignore page into sections (diff)
downloadtgif-6f02a5a33a3983597992e94c7b826021acc8a9d9.tar.xz
Documentation: point to related commands from gitignore
A frequently asked question on #git is how to stop tracking a file that is mistakenly tracked by git. A frequently attempted strategy is to add such files to .gitignore. Thus one might imagine that the gitignore documentation could be a good entry point for 'git rm' documentation. Add some cross-references in this vein. While at it, move a reference to update-index --assume-unchanged from the DESCRIPTION to lower down on the page. This way, the methodical reader can benefit from first learning what excludes files do, then how they relate to other git facilities. Based-on-patch-by: Sitaram Chamarty <sitaram@atc.tcs.com> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9134-git-svn-ignore-paths.sh')
0 files changed, 0 insertions, 0 deletions