From: Mark Levedahl <mdl123@verizon.net>
To: git@vger.kernel.org
Cc: Mark Levedahl <mdl123@verizon.net>
Subject: [PATCH] Add git-bundle - pack objects and references for disconnected transfer
Date: Thu, 15 Feb 2007 19:19:52 -0500 [thread overview]
Message-ID: <11715851972838-git-send-email-mdl123@verizon.net> (raw)
In-Reply-To: <11715851974102-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.sh | 103 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 103 insertions(+), 0 deletions(-)
create mode 100755 git-bundle.sh
diff --git a/git-bundle.sh b/git-bundle.sh
new file mode 100755
index 0000000..c431b52
--- /dev/null
+++ b/git-bundle.sh
@@ -0,0 +1,103 @@
+#!/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.tar 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 [--output=file] <git-rev-list arguments>'
+SUBDIRECTORY_OK=1
+. git-sh-setup
+
+# 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.tar
+nextisoutput=
+for arg in $myargs ; do
+ case "$arg" in
+ -h|--h|--he|--hel|--help)
+ echo "$USAGE"
+ exit;;
+ --output=*)
+ bfile=${arg##--output=};;
+ *)
+ die "unknown option: $arg";;
+ esac
+done
+
+# find the refs to carry along and get sha1s for each.
+refs=
+fullrevargs=
+for arg in $gitrevargs ; do
+ #ignore options and basis refs, get unambiguous ref name for things
+ # we will transport (e.g., user gives master, have heads/master and
+ # remotes/origin/master, we keep the former).
+ case "$arg" in
+ -*) fullrevargs="$fullrevargs $arg";;
+ ^*) fullrevargs="$fullrevargs $arg";;
+ *) ref=$(git-show-ref "$arg" | head -n1)
+ [ -z "$ref" ] && die "unknown reference: $arg"
+ fullrevargs="$fullrevargs ${ref#* }"
+ refs="$refs $ref"
+ ;;
+ esac
+done
+[ -z "$refs" ] && die "No references specified, I don't know what to bundle."
+
+# git-rev-list cannot determine edge objects if a date restriction is given...
+# we do things a slow way if max-age or min-age are given
+fast=
+[ "${fullrevargs##*--max-age}" == "$fullrevargs" ] && \
+[ "${fullrevargs##*--min-age}" == "$fullrevargs" ] && fast=1
+
+if [ -z "$fast" ] ; then
+ # get a list of all commits that will be packed along with parents of each.
+ # A fixed git-rev-list --boundary should replace all of this.
+ echo "Finding prerequisites and commits to bundle..."
+ commits=$(git-rev-list $fullrevargs)
+
+ # get immediate parents of each commit to include
+ parents=
+ for c in $commits ; do
+ parents="$parents $(git-rev-list --parents $c | head -1 | cut -b42-)"
+ done
+ parents=$(printf "%s\n" $parents | sort | uniq)
+
+ # factor out what will be in this bundle, the remainder are the bundle's pre-requisites.
+ # double up commits in this as we only want things that are only in parents to appear once
+ prereqs=$(printf "%s\n" $parents $commits $commits | \
+ sort | \
+ uniq -c | \
+ grep ' 1 ' \
+ | sed 's/ *1 //')
+else
+ prereqs=$(git-rev-list --objects-edge $fullrevargs | \
+ grep '^-' | sed 's/-//')
+fi
+
+# create refs and pack
+[ -e "$bfile" ] && rm -f "$bfile" 2>/dev/null
+printf "%s\n" $prereqs > .gitBundleReferences
+echo "-" >> .gitBundleReferences
+git-show-ref $refs >> .gitBundleReferences
+(git-rev-list --objects $fullrevargs | \
+ cut -b-40 | \
+ git pack-objects --all-progress --stdout >.gitBundlePack) \
+ || (rm -f "$bfile" ; exit)
+tar cf "$bfile" .gitBundleReferences .gitBundlePack
+tar cf "$bfile" .gitBundleReferences .gitBundlePack
+rm .gitBundleReferences .gitBundlePack
+
+# done
+echo "Created $bfile"
--
1.5.0.34.g6afaa
next prev parent reply other threads:[~2007-02-16 0:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 0:19 Respun - Scripts to use bundles to move data between repos Mark Levedahl
2007-02-16 0:19 ` Mark Levedahl [this message]
2007-02-16 0:19 ` [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Mark Levedahl
2007-02-16 0:19 ` [PATCH] Include git-bundle and git-unbundle in Makefile Mark Levedahl
2007-02-16 0:19 ` [PATCH] Create documentation for git-bundle Mark Levedahl
2007-02-16 0:19 ` [PATCH] Create documentation for git-unbundle Mark Levedahl
2007-02-16 0:19 ` [PATCH] Link git-bundle and git-unbundle docs from git(7) Mark Levedahl
2007-02-16 2:24 ` [PATCH] Add git-unbundle - unpack objects and references for disconnected transfer Junio C Hamano
2007-02-16 2:40 ` Linus Torvalds
2007-02-16 6:38 ` Mark Levedahl
2007-02-16 6:48 ` Shawn O. Pearce
2007-02-16 7:31 ` Junio C Hamano
2007-02-16 7:45 ` Shawn O. Pearce
2007-02-16 6:22 ` Mark Levedahl
2007-02-16 7:24 ` Junio C Hamano
2007-02-16 2:11 ` [PATCH] Add git-bundle - pack " Junio C Hamano
2007-02-16 4:41 ` Shawn O. Pearce
2007-02-16 7:28 ` Junio C Hamano
2007-02-16 6:39 ` Mark Levedahl
2007-02-16 6:54 ` Shawn O. Pearce
2007-02-16 11:57 ` Simon 'corecode' Schubert
2007-02-16 4:37 ` Respun - Scripts to use bundles to move data between repos Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2007-02-16 12:45 Re: [PATCH] Add git-bundle - pack objects and references for disconnected transfer Mark Levedahl
2007-02-16 13:25 ` Simon 'corecode' Schubert
2007-02-16 13:44 ` Johannes Schindelin
2007-02-16 23:25 ` Mark Levedahl
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=11715851972838-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).