From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "David Bremner" <bremner@unb.ca>,
"Kristian Høgsberg" <krh@redhat.com>,
git@vger.kernel.org, 469250@bugs.debian.org
Subject: Re: Commit f5bbc322 to git broke pre-commit hooks which read stdin
Date: Tue, 04 Mar 2008 03:51:22 -0800 (PST) [thread overview]
Message-ID: <m3k5kiiu60.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LSU.1.00.0803041044120.22527@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 4 Mar 2008, David Bremner wrote:
>
>> It looks like line 435 of builtin-commit.c disables stdin for hooks
>> (with the disclaimer that I first looked at the git source ten minutes
>> ago).
>>
>> hook.no_stdin = 1
>>
>> I'm not sure if this was by design, but just so you know, this breaks
>> people's hooks. In particular the default metastore pre-commit hook no
>> longer works. I didn't find anything relevant in the docs [1].
>
> Pardon my ignorance, but what business has metastore reading stdin? There
> should be nothing coming in, so the change you mentioned should be
> correct, and your hook relies on something it should not rely on.
Never mind pre-commit. What about pre-receive and post-receive hooks,
both of which gets data on stdin?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-03-04 11:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 8:38 Bug#469250: Commit f5bbc322 to git broke pre-commit hooks which read stdin David Bremner
2008-03-04 10:45 ` Johannes Schindelin
2008-03-04 11:12 ` Junio C Hamano
2008-03-04 11:48 ` Johannes Sixt
2008-03-04 12:17 ` Junio C Hamano
2008-03-04 11:48 ` David Bremner
2008-03-04 12:04 ` Johannes Schindelin
2008-03-04 18:16 ` Joey Hess
2008-03-04 22:15 ` David Bremner
2008-03-05 5:12 ` Shawn O. Pearce
2008-03-05 5:36 ` Junio C Hamano
2008-03-05 5:46 ` Shawn O. Pearce
2008-03-04 11:51 ` Jakub Narebski [this message]
2008-03-04 12:03 ` Johannes Schindelin
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=m3k5kiiu60.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=469250@bugs.debian.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=bremner@unb.ca \
--cc=git@vger.kernel.org \
--cc=krh@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox