pre-receive hook output not echoed to terminal

[Christopher Simons]

Greetings,

I'm trying out Git for Windows for the first time, and I noticed that Git for

Windows doesn't echo output from our pre-receive hooks (example below), at

least with the default configuration.  Is this behavior configurable, or has

this not yet been implemented in Git for Windows?

Details follow:

On Git for Windows, I just get the following (notice absence of hook output):

$ git version

git version 2.7.0.windows.2

$ git push

Counting objects: 3, done.

Writing objects: 100% (3/3), 267 bytes | 0 bytes/s, done.

Total 3 (delta 0), reused 0 (delta 0)

To git://viadevgit01/test.git

 ! [remote rejected] master -> master (pre-receive hook declined)

error: failed to push some refs to 'git://viadevgit01/test.git'

$

On Git from the Cygwin distribution I get the following (notice hook output):

$ git version

git version 2.5.3

$ git push

Counting objects: 3, done.

Writing objects: 100% (3/3), 267 bytes | 0 bytes/s, done.

Total 3 (delta 0), reused 0 (delta 0)

remote: diff sig: 836118a152fb9a77e5f215545573c05f17af7511..2c63ea10c9aeb9349b75467e886ce18cc10f6d61

remote: (!!!) Unauthorized committer: per...@company.com

remote: exit status 1

remote: (!!!) Nonconformant commit message: add 'tags' to .gitignore

remote: exit status 1

To git://viadevgit01/test.git

 ! [remote rejected] master -> master (pre-receive hook declined)

error: failed to push some refs to 'git://viadevgit01/test.git'

$

Regards,

Christopher Simons

Pittsburgh, PA

[Johannes Schindelin]

Hi Christopher,

On Thu, 4 Feb 2016, Christopher Simons wrote:

> I noticed that Git for Windows doesn't echo output from our pre-receive
> hooks (example below), at least with the default configuration. Is this
> behavior configurable, or has this not yet been implemented in Git for
> Windows?

We had some problems with sideband support (which is the feature of the
transport protocol responsible to transport stdout/stderr) for some time.
That was in Git for Windows 1.x times, though, and I am not aware that Git
for Windows 2.x shares that problem.

So it must be something different.

Ciao,
Johannes