git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
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 16:00:14 -0400	[thread overview]
Message-ID: <CAPZPVFaJ0qOhxMYDxhq4+qnWQjjhFRUjzGAemqjwAAoxC8-EDQ@mail.gmail.com> (raw)
In-Reply-To: <CALWbr2ynF425qfCNr_NGH8z9UiX2G2CRrWiCo2XrgBLBbyPHMw@mail.gmail.com>

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 <apelisse@gmail.com> wrote:
> On Mon, Jun 3, 2013 at 8:02 PM, Eugene Sajine <euguess@gmail.com> 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
> git-daemon with "--informative-errors" if you want to allow custom
> errors. Maybe there is place for improvement in the documentation.
>
> Cheers,

      reply	other threads:[~2013-06-03 20:00 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
2013-06-03 19:05     ` Antoine Pelisse
2013-06-03 20:00       ` Eugene Sajine [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPZPVFaJ0qOhxMYDxhq4+qnWQjjhFRUjzGAemqjwAAoxC8-EDQ@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).