All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joey Hess <joey@kitenet.net>
To: Chris Patti <cpatti@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug: git-hooks documentation should note that if you are using git-daemon you will *not* see stdout and stderr output from hooks.
Date: Wed, 1 Sep 2010 13:41:03 -0400	[thread overview]
Message-ID: <20100901174103.GA23445@gnu.kitenet.net> (raw)
In-Reply-To: <AANLkTi=H-W2zVcW_qK-BR8hRZvrv2EhY06Z_JfYYLFQR@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Chris Patti wrote:
> How can I go about submitting a bug or a change request or a diff or
> whatever to get this fixed please?
> 
> It's exceedingly confusing for someone just learning about hook
> development, and wasted a few hours of my time I'd rather have spent
> getting my hook running :)

For stderr, git-daemon used to not propigate it, but 
that was fixed (in 5d87dd4fcac808fc0f0b993b470644ba7d2d62a2 / 1.6.4),
at least for git-daemon started with --detach or --inetd.

IIRC, all it took to get it fixed was me complaining on this list and
the wonderful git developers seeing it. :)

For example:

joey@gnu:~/src/ikiwiki/doc>git push git://ikiwiki.info/
Counting objects: 10, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 599 bytes, done.
Total 6 (delta 4), reused 0 (delta 0)
remote: removal of attachments is not allowed  <-- stderr from my hook
To git://ikiwiki.info/
 ! [remote rejected] master -> master (pre-receive hook declined)

-- 
see shy jo

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2010-09-01 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 17:05 Bug: git-hooks documentation should note that if you are using git-daemon you will *not* see stdout and stderr output from hooks Chris Patti
2010-09-01 17:41 ` Joey Hess [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

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

  git send-email \
    --in-reply-to=20100901174103.GA23445@gnu.kitenet.net \
    --to=joey@kitenet.net \
    --cc=cpatti@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.