From: Mark Levedahl <mdl123@verizon.net>
To: git@vger.kernel.org
Cc: Mark Levedahl <mdl123@verizon.net>
Subject: [PATCH] git-bundle - bundle objects and references for disconnected transfer.
Date: Wed, 14 Feb 2007 09:10:26 -0500 [thread overview]
Message-ID: <11714622292295-git-send-email-mdl123@verizon.net> (raw)
In-Reply-To: <11714622292110-git-send-email-mdl123@verizon.net>
Some workflows require coordinated development between repositories on
machines that can never be connected. This utility creates a bundle
containing a pack of objects and associated references (heads or tags)
that can be independently transferred to another machine, effectively
supporting git-push like operations between disconnected systems.
Signed-off-by: Mark Levedahl <mdl123@verizon.net>
---
git-bundle | 85 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 85 insertions(+), 0 deletions(-)
create mode 100755 git-bundle
diff --git a/git-bundle b/git-bundle
new file mode 100755
index 0000000..1341885
--- /dev/null
+++ b/git-bundle
@@ -0,0 +1,85 @@
+#!/bin/sh
+# Create a bundle to carry from one git repo to another (e.g., "sneaker-net" based push)
+# git-bundle <git-rev-list args>
+# git-bundle --bare <git-rev-list args>
+# creates bundle.zip in current directory (can rename of course)
+#
+# The bundle includes all refs given (--all selects every ref in the repo).
+# and all of the commit objects needed subject to the list given.
+#
+# Objects to be packed are limited by specifying one or more of
+# ^commit-ish - indicated commits already at the target (can have more than one ^commit-ish)
+# --since=xxx - Assume target repo has all relevant commits earlier than xxx
+
+USAGE='git-bundle <options> <git-rev-list arguments>
+
+Creates a bundle of objects to be carried to a disconnected repository, bringing the target
+repository''s definition of one or more references up to date as selected by the
+<git-rev-list arguments>
+
+Options:
+ -h, --help Print this help screen
+ --bare Work in a bare repository
+ --output=f Output to file f (default is bundle.zip)
+
+ examples
+ git-bundle master~10..master
+ git-bundle master next pu ^master~30 --output=mybundle.zip --bare'
+
+die() {
+ echo >&2 "$@"
+ exit 1
+}
+
+# pull out rev-list args vs program args, parse the latter
+gitrevargs=$(git-rev-parse --symbolic --revs-only $*) || exit 1
+myargs=$(git-rev-parse --no-revs $*) || exit 1
+
+bfile=bundle.zip
+for arg in $myargs ; do
+ case "$arg" in
+ --bare)
+ export GIT_DIR=.;;
+ -h|--h|--he|--hel|--help)
+ echo "$USAGE"
+ exit;;
+ --output=*)
+ bfile=${arg##--output=};;
+ -*)
+ die "unknown option: $arg";;
+ *)
+ esac
+done
+
+GIT_DIR=$(git-rev-parse --git-dir) || die "Not in a git directory"
+
+# find the refs to carry along and get sha1s for each.
+refs=
+for arg in $gitrevargs ; do
+ #ignore options and basis refs
+ case "$arg" in
+ ^*) ;;
+ -*) ;;
+ *)
+ n=$(git-show-ref "$arg" | wc -l)
+ [ $n -eq 1 ] || die "ambiguous reference: $arg"
+ refs="$refs $arg"
+ ;;
+ esac
+done
+[ -z "$refs" ] && die "No references specified, I don't know what to bundle."
+
+# put the refs into the bundle file
+[ -e "$bfile" ] && rm -f "$bfile" 2>/dev/null
+git-show-ref $refs > .gitBundleReferences
+zip -m "$bfile" .gitBundleReferences
+
+# add the pack file
+(git-rev-list --objects $gitrevargs | \
+ cut -b -40 | \
+ git pack-objects --all-progress --progress --stdout >.gitBundlePack) \
+ || (rm -f "$bfile" ; exit)
+zip -m "$bfile" .gitBundlePack
+
+# done
+echo "Created $bfile"
--
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 ` Mark Levedahl [this message]
2007-02-14 14:10 ` [PATCH] git-unbundle - unbundle objects and references for disconnected transfer Mark Levedahl
2007-02-14 14:10 ` [PATCH] Create a man page for git-bundle Mark Levedahl
2007-02-14 14:10 ` [PATCH] Create a man page for git-unbundle Mark Levedahl
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=11714622292295-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).