From 1164789a5967426e1488e3b09c88974af5f9580d Mon Sep 17 00:00:00 2001
From: Simon Hausmann <simon@luria.(none)>
Date: Sun, 8 Apr 2007 10:21:56 +0200
Subject: [PATCH] Added a simple example of usage to the "documentation" :)

---
 git-p4.txt | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/git-p4.txt b/git-p4.txt
index 99ae85b..4f6a680 100644
--- a/git-p4.txt
+++ b/git-p4.txt
@@ -103,3 +103,25 @@ continue importing the remaining changes with
 
 After submitting you should sync your perforce import branch ("p4" or "origin")
 from Perforce using git-p4's sync command.
+
+
+Example
+=======
+
+# Clone a repository
+  git-p4 clone //depot/path/project
+# Enter the newly cloned directory
+  cd project
+# Do some work...
+  vi foo.h
+# ... and commit locally to gi
+  git commit foo.h
+# In the meantime somebody submitted changes to the Perforce depot. Rebase your latest
+# changes against the latest changes in Perforce:
+  git-p4 rebase
+# Submit your locally committed changes back to Perforce
+  git-p4 submit
+# ... and synchronize with Perforce
+  git-p4 rebase
+
+
-- 
2.11.4.GIT