On Mon, 29 Jul 2013 11:22:38 -0400
wor...@alum.mit.edu (Dale R. Worley) wrote:
[...]
> I don't know the official specification (and it's not likely to have
> been written down anywhere), but it is possible that the directory for
> remote operations *must* be a *bare* repository.
[...]
To my knowl
The problem seems to be that the Git process on the remote end has a
current working directory that it doesn't think is a Git reponsitory.
Most likely this is because the Git remote link has directed the
remote process to be in a directory that *isn't* a Git repository. Is
there any way that you
On Mon, 29 Jul 2013 06:06:32 -0700 (PDT)
Andreas Dvorak wrote:
> I found the solution. With env -i to unset the environment the git
> command does work
> #!/bin/sh
> DATE_STAMP=$(date +%Y%m%d%H%M)
> LOG=/var/tmp/git.log
> echo "checkout $DATE_STAMP" >>$LOG
> cd /var/tmp/test2_clone
> env -i git f
On Mon, 29 Jul 2013 03:50:56 -0700 (PDT)
Andreas Dvorak wrote:
> Hi Krishna,
>
> unfortunately that did not help. The output is the same.
> DATE_STAMP=$(date +%Y%m%d%H%M)
> LOG=/var/tmp/git.log
> echo "checkout $DATE_STAMP" >>$LOG
> cd /var/tmp/test2_clone
> GIT_TRACE=1
> git fetch origin
^^^
