From: Mark Levedahl <mdl123@verizon.net>
To: git@vger.kernel.org
Cc: Mark Levedahl <mdl123@verizon.net>
Subject: [PATCH] Create a man page for git-unbundle.
Date: Wed, 14 Feb 2007 09:10:29 -0500 [thread overview]
Message-ID: <1171462229415-git-send-email-mdl123@verizon.net> (raw)
In-Reply-To: <11714622291709-git-send-email-mdl123@verizon.net>
Signed-off-by: Mark Levedahl <mdl123@verizon.net>
---
Documentation/git-unbundle.txt | 55 ++++++++++++++++++++++++++++++++++++++++
1 files changed, 55 insertions(+), 0 deletions(-)
create mode 100644 Documentation/git-unbundle.txt
diff --git a/Documentation/git-unbundle.txt b/Documentation/git-unbundle.txt
new file mode 100644
index 0000000..8dbfccb
--- /dev/null
+++ b/Documentation/git-unbundle.txt
@@ -0,0 +1,55 @@
+git-unbundle(1)
+================
+
+NAME
+----
+git-unbundle - Unpackage objects and refs to update a disconnected repository
+
+
+SYNOPSIS
+--------
+'git-unbundle' [--bare ] [--force] [--shallow] file
+
+DESCRIPTION
+-----------
+
+Some workflows require that one or more branches of development on one machine
+be replicated on another machine, but the two machines cannot be directly
+connected so the gitlink:git-fetch[1] protocol cannot be used. This command
+unpacks a bundle file created by gitlink:git-bundle[1] on another repository,
+adding the objects and updating references as defined by the donor repository.
+
+OPTIONS
+-------
+
+--bare::
+ Assume operation in a bare repository.
+
+--force::
+ Normally only fast-forward reference updates are performed. Specifying
+ this option allows non-fast forward updates.
+
+--shallow::
+ Normally, git-fsck is invoked on each reference to assure there are no
+ missing objects. This option bypasses that checking, allowing shallow
+ copies. Use with caution, many git operations are not supported on
+ shallow repositories.
+
+file::
+ Bundle file created by gitlink:git-bundle[1]. Default is bundle.zip.
+
+ERROR CHECKING
+--------------
+
+In addition to the checks mentioned under --force and --shallow above,
+git-unbundle uses gitlink:git-unpack-objects[1] to update objects, and
+gitlink:git-update-ref to update all references, and thus all the inherent
+safety checks provided by those functions are in force.
+
+Author
+------
+Written by Mark Levedahl <mdl123@verizon.net>
+
+GIT
+---
+Part of the gitlink:git[7] suite
--
1.5.0.rc3.24.g0c5e
next prev parent reply other threads:[~2007-02-14 14:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 14:10 Scripts to use "bundles" for moving data between repositories Mark Levedahl
2007-02-14 14:10 ` [PATCH] git-bundle - bundle objects and references for disconnected transfer Mark Levedahl
2007-02-14 14:10 ` [PATCH] git-unbundle - unbundle " Mark Levedahl
2007-02-14 14:10 ` [PATCH] Create a man page for git-bundle Mark Levedahl
2007-02-14 14:10 ` Mark Levedahl [this message]
2007-02-14 19:45 ` [PATCH] git-unbundle - unbundle objects and references for disconnected transfer Shawn O. Pearce
2007-02-14 20:57 ` Mark Levedahl
2007-02-14 21:03 ` Shawn O. Pearce
2007-02-14 22:43 ` Mark Levedahl
2007-02-14 21:18 ` Nicolas Pitre
2007-02-14 19:42 ` [PATCH] git-bundle - bundle " Shawn O. Pearce
2007-02-14 21:58 ` Johannes Schindelin
2007-02-14 23:19 ` Mark Levedahl
2007-02-14 23:55 ` Mark Levedahl
2007-02-15 0:15 ` Johannes Schindelin
2007-02-15 2:13 ` Mark Levedahl
2007-02-15 15:35 ` Johannes Schindelin
2007-02-15 0:07 ` Johannes Schindelin
2007-02-15 2:32 ` Mark Levedahl
2007-02-15 15:32 ` Johannes Schindelin
2007-02-16 0:12 ` Mark Levedahl
2007-02-16 0:40 ` Johannes Schindelin
2007-02-16 3:23 ` Mark Levedahl
2007-02-14 14:13 ` Scripts to use "bundles" for moving data between repositories Matthieu Moy
2007-02-14 14:37 ` Mark Levedahl
2007-02-14 15:46 ` Johannes Schindelin
2007-02-14 17:11 ` Junio C Hamano
2007-02-14 17:56 ` Mark Levedahl
2007-02-14 18:00 ` Junio C Hamano
2007-02-14 21:24 ` Mark Levedahl
2007-02-14 21:26 ` Junio C Hamano
2007-02-14 18:20 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1171462229415-git-send-email-mdl123@verizon.net \
--to=mdl123@verizon.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).