git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to handle terminal detection in a daemon calling git?

From
TPTravis P <git@castle.fastmail.fm>
Date
May 30, 2012, 21:16 UTC
Message-ID
<1338412607.9452.140661082904349.02F677C3@webmail.messagingengine.com>

I've got a script that runs in the background without a terminal. It actually does have STDOUT and STDERR set to a rotating log file.

When it runs:
  /bin/sh -c 'cd /to/my/wc; git pull --ff-only'
the git command fails (rc 32768).
When it runs
 /bin/sh -c 'cd /to/my/wc; git pull --ff-only > /to/a/file 2>&1'
or even
 /bin/sh -c 'cd /to/my/wc; git pull --ff-only | cat'

then all is well. The command succeeds (rc 0, and I see the expected results).

Piping through 'cat' is okay, but I'd rather avoid the 'trick'. Is there some way to communicate to git that it should operate just as if output were redirected?

-Travis
Next: Jeff King
Message 1 of 9 in “How to handle terminal detection in a daemon calling git?”
  1. Travis PMay 30, 2012
  2. Jeff KingMay 31, 2012
  3. Junio C HamanoMay 31, 2012
  4. Travis PMay 31, 2012
  5. Jeff KingJun 1, 2012
  6. TravisJun 1, 2012
  7. Jeff KingJun 2, 2012
  8. Travis PMay 31, 2012
  9. Sitaram ChamartyMay 31, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.