From: "Gustav Hållberg" <gustav@gmail.com>
To: git@vger.kernel.org
Subject: git {pull,push} fails without stdin
Date: Wed, 28 Jan 2009 10:27:14 +0100 [thread overview]
Message-ID: <a1e915350901280127g55d6a978i241c2b9793cc8690@mail.gmail.com> (raw)
This was seen in git 1.6.0.2...
I want to run "git push" in an automated system and, as there's no
sensible stdin to use, I close fd 0 before exec'ing.
However, it does not work:
sh$ git push <&-
fatal: read error (Bad file descriptor)
compared to:
sh$ git push
Everything up-to-date
The same thing happens with "git pull", but not the other git commands
I tried (in a far-from-exhaustive search).
It's trivial to work around (e.g., use /dev/null as stdin), but it
would be more convenient if it just worked :-)
- Gustav
reply other threads:[~2009-01-28 9:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a1e915350901280127g55d6a978i241c2b9793cc8690@mail.gmail.com \
--to=gustav@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 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).