If you don't copy these over, you may get a surprising error message when you try to do a I would recommend copying those files over first and then trying to run git to see if it complains about any missing shared libraries.If it doesn't, then you are (presumably) good to go. (No use copying over shared libraries if they already exist on the target host and are the correct version.) You can copy the files with --exec-path Path to wherever your core git programs are installed.

Signed-off-by: Junio C Hamano --- builtin-receive-pack.c | 58 ------------ t/t5516| 6 -- 2 files changed, 46 insertions( ), 18 deletions(-) diff --git a/builtin-receive-pack.c b/builtin-receive-pack.c index 6564a97..f2c94fc 100644 --- a/builtin-receive-pack.c b/builtin-receive-pack.c @@ -12,6 12,7 @@ static const char receive_pack_usage[] = "git-receive-pack "; enum deny_action { DENY_UNCONFIGURED, DENY_IGNORE, DENY_WARN, DENY_REFUSE, @@ -19,7 20,7 @@ enum deny_action static char *warn_unconfigured_deny_msg[] = ; static void warn_unconfigured_deny(void) static const char *update(struct command *cmd) - switch (deny_current_branch) { - case DENY_IGNORE: - break; - case DENY_WARN: - if (! has_sha1_file(new_sha1)) { diff --git a/t/t5516b/t/t5516index 4426df9..89649e7 100755 --- a/t/t5516b/t/[email protected]@ -492,7 492,7 @@ test_expect_success 'warn on push to HEAD of non-bare repository' ' git checkout master && git config Current Branch warn) && git push testrepo master 2stderr && - grep "warning.*this may cause confusion" stderr grep "warning: updating the current branch" stderr ' test_expect_success 'deny push to HEAD of non-bare repository' ' @@ -510,7 510,7 @@ test_expect_success 'allow push to HEAD of bare repository (bare)' ' git config Current Branch true && git config true) && git push testrepo master 2stderr && - ! grep "warning: updating the current branch" stderr ' test_expect_success 'allow push to HEAD of non-bare repository (config)' ' @@ -520,7 520,7 @@ test_expect_success 'allow push to HEAD of non-bare repository (config)' ' git config Current Branch false ) && git push testrepo master 2stderr && - !

is_ref_checked_out(name)) if (is_ref_checked_out(name)) if (!

If you push from your local machine to the remote, you will only be updating files in the repository and not the working copy. This can be confusing because you might log into the remote after you push an expect the working copy to be different.

To deal with this possible confusion from the remote like you might a central svn server. Say I have an existing git repository on my local machine and I want to create a new remote to back it up.

Maybe if I attempt to build git statically with openssl, but it feels like a bad idea too.

$ git remote add godaddy ssh://[email protected]//home/content/u/n/c/unclecj/$ git push godaddy master bash: git-receive-pack: command not found fatal: The remote end hung up unexpectedly $ git push --receive-pack="/home/content/u/n/c/unclecj/opt/git-1.6.3/bin/git-receive-pack" godaddy master /home/content/u/n/c/unclecj/opt/git-1.6.3/bin/git-receive-pack: error while loading shared libraries: 0.9.8: cannot open shared object file: No such file or directory fatal: The remote end hung up unexpectedly Off topic, but is this the sort of lack of support I should expect from godaddy, should I regret not choosing dreamhosts instead? Not an answer, but a suggestion that once git-receive is working on godaddy (is it?

They don't even have to be running the same distribution or version of Linux, as long as they're the same architecture and you can find the binaries and library files you need.

To find the location of the main git binary: Other important files are that git depends on are under a 'libexec' directory somewhere on the source system.

, making it rather difficult to download and install git for your user.

The only way I could think of to work around these restrictions was to copy over the git binaries over from another computer that had them.

You want to eventually change the default to deny, and there is no point to teach how to allow it to people who set the config to deny themselves, nor to new people who created their repository with updated git-clone.