Doc cleanups.

Signed-off-by: Simon Hausmann <simon@lst.de>

diff --git a/contrib/fast-import/git-p4.txt b/contrib/fast-import/git-p4.txt
index 4f6a680f95f2c3f11a25bb0f0c795dab4bcc5419..d36a1cf18c09785dd6a44b85837877dfb8c912d9 100644 (file)
--- a/contrib/fast-import/git-p4.txt
+++ b/contrib/fast-import/git-p4.txt
@@ -4,8 +4,8 @@ Usage
 =====
 
 git-p4 supports two main modes: Importing from Perforce to a Git repository is
 =====
 
 git-p4 supports two main modes: Importing from Perforce to a Git repository is

-done using "git-p4 sync". Submitting changes from Git back to Perforce is
-done using "git-p4 submit".
+done using "git-p4 sync" or "git-p4 rebase". Submitting changes from Git back
+to Perforce is done using "git-p4 submit".

 
 Importing
 =========
 
 Importing
 =========


@@ -49,10 +49,6 @@ a big import. This may take a while.
 Support for Perforce integrations is still work in progress. Don't bother
 trying it unless you want to hack on it :)
 
 Support for Perforce integrations is still work in progress. Don't bother
 trying it unless you want to hack on it :)
 

-For convenience there's also the git-p4 clone command that works similar to
-git-clone and combines the creation of the git repository with the the initial
-import and the branch setup
-

 Incremental Imports
 ===================
 
 Incremental Imports
 ===================