]> git.madduck.net Git - code/vcsh.git/commitdiff

madduck's git repository

Every one of the projects in this repository is available at the canonical URL git://git.madduck.net/madduck/pub/<projectpath> — see each project's metadata for the exact URL.

All patches and comments are welcome. Please squash your changes to logical commits before using git-format-patch and git-send-email to patches@git.madduck.net. If you'd read over the Git project's submission guidelines and adhered to them, I'd be especially grateful.

SSH access, as well as push access can be individually arranged.

If you use my repositories frequently, consider adding the following snippet to ~/.gitconfig and using the third clone URL listed for each project:

[url "git://git.madduck.net/madduck/"]
  insteadOf = madduck:

add sample hooks that allow cloning over extant files
authorCaleb Maclennan <caleb@alerque.com>
Sun, 20 Oct 2013 01:35:10 +0000 (19:35 -0600)
committerCaleb Maclennan <caleb@alerque.com>
Wed, 5 Feb 2014 12:45:10 +0000 (14:45 +0200)
Cloning a repo over an existing set of files would usually
cause a merge conflict that aborts the process and requires
manual intervention. This pair of hooks handles that case
by manually moving the extant objects out of the way,
completing the checktout, then restoring them to their
original places. The resulting state is a set of unstaged
local changes.

doc/hooks
doc/sample_hooks/post-merge-unclobber [new file with mode: 0755]
doc/sample_hooks/pre-merge-unclobber [new file with mode: 0755]

index 30cd373a50b492b472edffe498e9ac63cff45516..282ee86265c765c7a457234931aaed000ae913aa 100644 (file)
--- a/doc/hooks
+++ b/doc/hooks
@@ -15,11 +15,11 @@ Available hooks are:
 * pre-init
 * post-init
 * pre-merge
 * pre-init
 * post-init
 * pre-merge
-    Use this hook to detect and handle merge conflicts before vcsh's native code
+       Use this hook to detect and handle merge conflicts before vcsh's native code
        finds and errors on them. This is useful for allowing clones on top of existing
        files.
 * post-merge
        finds and errors on them. This is useful for allowing clones on top of existing
        files.
 * post-merge
-    Use this hook to finish handling any merge conflicts found in the pre-merge hook.
+       Use this hook to finish handling any merge conflicts found in the pre-merge hook.
 * pre-pull
 * post-pull
 * pre-push
 * pre-pull
 * post-pull
 * pre-push
diff --git a/doc/sample_hooks/post-merge-unclobber b/doc/sample_hooks/post-merge-unclobber
new file mode 100755 (executable)
index 0000000..017a13f
--- /dev/null
@@ -0,0 +1,10 @@
+#!/bin/sh
+
+# This finds objects that the pre-merge script moved out of the way to
+# avoid conflicts when running git clone and moves them back to their
+# original places. The result is that the git repository gets checked out
+# and the extant objects end up back in the working directory. Git now
+# sees these as un-staged changes to the working branch and you can deal
+# with them by adding them or reverting.
+
+find -name '*.vcsh-unclobber' -execdir rename .vcsh-unclobber '' {} \;
diff --git a/doc/sample_hooks/pre-merge-unclobber b/doc/sample_hooks/pre-merge-unclobber
new file mode 100755 (executable)
index 0000000..93a7319
--- /dev/null
@@ -0,0 +1,11 @@
+#!/bin/sh
+
+# This code does amost exactly what the native VCSH sanity checking code
+# does except that on finding a potential merge conflict, it moves the 
+# extant object out of the way temporarily. The merge then happens cleanly
+# as far as git knows, and a post-merge hook can figure out what to do with
+# the extant versions of the objects.
+
+for object in $(git ls-tree -r origin/master | awk '{print $4}'); do
+       [ -e "$object" ] && mv "$object" "$object.vcsh-unclobber" 
+done