[PATCH 2/3] git-bundle.txt: Bundles as [remote ""] is a feature, not an example
Signed-off-by: Santi Béjar <sbejar@gmail.com>
---
Documentation/git-bundle.txt | 38 ++++++++++++++++++++------------------
1 files changed, 20 insertions(+), 18 deletions(-)
diff --git a/Documentation/git-bundle.txt b/Documentation/git-bundle.txt
index 72f080a..1143cdc 100644
--- a/Documentation/git-bundle.txt
+++ b/Documentation/git-bundle.txt
@@ -92,6 +92,26 @@ It is okay to err on the side of conservatism, causing the bundle file
to contain objects already in the destination as these are ignored
when unpacking at the destination.
+REMOTES
+-------
+
+With something like this in your config:
+
+[remote "bundle"]
+ url = /path/to/file.bdl
+ fetch = refs/heads/*:refs/remotes/bundle/*
+
+You can place a bundle in /path/to/file.bdl and then these commands:
+
+------------
+$ git ls-remote bundle
+$ git fetch bundle
+$ git pull bundle
+------------
+
+would treat it as if it is talking with a remote side over the
+network.
+
EXAMPLE
-------
@@ -121,24 +141,6 @@ $ git-fetch mybundle refspec
where refspec is refInBundle:localRef
-Also, with something like this in your config:
-
-[remote "bundle"]
- url = /home/me/tmp/file.bdl
- fetch = refs/heads/*:refs/remotes/origin/*
-
-You can first sneakernet the bundle file to ~/tmp/file.bdl and
-then these commands:
-
-------------
-$ git ls-remote bundle
-$ git fetch bundle
-$ git pull bundle
-------------
-
-would treat it as if it is talking with a remote side over the
-network.
-
Author
------
Written by Mark Levedahl <mdl123@verizon.net>
--
1.5.4.3.293.gac81