Right, --informative-errors does make it better;)
Actually the CWD for the access-hook is not where the hook script is,
but inside the .git folder of the target repo. GTK.
and yes, definitely some documentation improvements needed;)
Thanks!
On Mon, Jun 3, 2013 at 3:05 PM, Antoine Pelisse wrote
On Mon, Jun 3, 2013 at 8:02 PM, Eugene Sajine wrote:
> Would you be able to advise how this should be done?
> I don't get the error message (i mean the output of pwd) if i do this:
>
> echo `pwd`
> exit 1
>
> What should it be?
Actually, after digging into the code, it looks like you need to call
> - Your log file might not be located where you expect, you should use
> absolute path to dump text
You were right! The problem was with the script itself - the log file
not being specified with absolute path! Stupid me!
...
> - The documentation says you can print one line before a failure, als
On Fri, May 31, 2013 at 10:22 PM, Eugene Sajine wrote:
> and trying to perform some operations like fetch or push. It is cloned
> and fetches and pushes successfully.
> The problem is that the file test_hook_out.txt doesn't have anything
> in it after the execution, So the hook doesn't seem to wor
Anybody? Any ideas?
Thanks in advance!
Eugene
On Fri, May 31, 2013 at 4:22 PM, Eugene Sajine wrote:
> Hi,
>
> I'm trying to test this new feature and having problems getting any
> results in the following scenario:
>
> i have a repo in local folder
>
> /home/users/myuser/repos/projectA/.git
>
>
Hi,
I'm trying to test this new feature and having problems getting any
results in the following scenario:
i have a repo in local folder
/home/users/myuser/repos/projectA/.git
i start the daemon with the following:
git daemon --export-all --base-path=/home/users/myuser/repos
--enable=receive-p
6 matches
Mail list logo
