From 64756e9940592f134a829da63de53764fb21ab69 Mon Sep 17 00:00:00 2001 From: Phil Jackson Date: Tue, 6 Jul 2010 11:03:18 +0100 Subject: [PATCH] Update manual with regards to the svn change. --- magit.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/magit.texi b/magit.texi index fbbb9eae..6c201330 100644 --- a/magit.texi +++ b/magit.texi @@ -679,13 +679,13 @@ Magit shows them in a section called @emph{Unpulled changes}. Typing @node Interfacing with Subversion @chapter Interfacing with Subversion -Typing @kbd{N r} runs @code{git svn rebase} and typing @kbd{N c} runs -@code{git svn dcommit}. +Typing @kbd{N r} runs @code{git svn rebase}, typing @kbd{N c} runs +@code{git svn dcommit} and typing @kbd{N f} runs @code{git svn fetch}. -@kbd{N f} will prompt you for a (numeric, Subversion) revision and +@kbd{N s} will prompt you for a (numeric, Subversion) revision and then search for a corresponding Git sha1 for the commit. This is limited to the path of the remote Subversion repository. With a prefix -(@kbd{C-u N f} the user will also be prompted for a branch to search +(@kbd{C-u N s} the user will also be prompted for a branch to search in. @node Using Git Directly