git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: cygwin: t3200-branch.sh fails with "List form of pipe open not implemented at -e line 22."
Date: Sun, 16 Oct 2005 00:46:49 -0700	[thread overview]
Message-ID: <7vbr1peweu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 20051015211808.GA3497@steel.home

Alex Riesen <raa.lkml@gmail.com> writes:

>> >The message comes from one of the hooks, which are executed even
>> >though they never meant to, because cygwin apparently uses file
>> >content or name to detect executability (on FAT).

Is this one of the hooks we ship as examples?  If so, that
means worse brokenness than just test failing.  It means that
the hook is not usable in your environment.

I presume it is this line in pre-commit sample hook:

    open $fh, "-|", qw(git-diff-index -p -M --cached HEAD);

Is Perl on Cygwin incapable of handle this in general, or is it
just what is on your machine being behind?

In the meantime, I've changed two things:

 - Earlier, tests run in a trash/ repository that was
   initialized with user's random templates.  This was *wrong*.
   It now uses freshly built templates that came from the
   source.

 - Further, hooks are disabled in the trash/ repository used for
   tests.  When we later add tests for hooks (HINTS, anybody
   ;-)), they can add their own anyway.

  reply	other threads:[~2005-10-16  7:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 12:46 cygwin: t3200-branch.sh fails with "List form of pipe open not implemented at -e line 22." Alex Riesen
2005-10-14 16:09 ` Junio C Hamano
2005-10-14 17:57 ` H. Peter Anvin
2005-10-15 21:18   ` Alex Riesen
2005-10-16  7:46     ` Junio C Hamano [this message]
2005-10-17  8:40       ` Alex Riesen

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=7vbr1peweu.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@gmail.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;
as well as URLs for NNTP newsgroup(s).