From: Eugene Sajine <euguess@gmail.com>
To: Antoine Pelisse <apelisse@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git daemon --access-hook problem
Date: Mon, 3 Jun 2013 14:02:56 -0400 [thread overview]
Message-ID: <CAPZPVFYdeuusW3=iBTBC+iPuOeAekvtMx6d_dozB9tsDCg3C8Q@mail.gmail.com> (raw)
In-Reply-To: <CALWbr2ypPCoftVLfP9uKeKStg3TWwLDchkUaL1d9s9O3kcuPwA@mail.gmail.com>
> - 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, also
> try this to show the cwd
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?
Thanks!
Eugene
>
> Hope that helps,
> Antoine,
next prev parent reply other threads:[~2013-06-03 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 20:22 git daemon --access-hook problem Eugene Sajine
2013-06-03 0:33 ` Eugene Sajine
2013-06-03 17:20 ` Antoine Pelisse
2013-06-03 18:02 ` Eugene Sajine [this message]
2013-06-03 19:05 ` Antoine Pelisse
2013-06-03 20:00 ` Eugene Sajine
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='CAPZPVFYdeuusW3=iBTBC+iPuOeAekvtMx6d_dozB9tsDCg3C8Q@mail.gmail.com' \
--to=euguess@gmail.com \
--cc=apelisse@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.