Git development
 help / color / mirror / Atom feed
From: "Tom Tanner (BLOOMBERG/ LONDON)" <ttanner2@bloomberg.net>
To: gitster@pobox.com, john@keeping.me.uk
Cc: davvid@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH] difftool: always honor "command not found" exit code
Date: Mon, 15 Aug 2016 10:38:23 -0000	[thread overview]
Message-ID: <57B19B9F0205070000390238_0_29566@p057> (raw)

Would it be possible to also treat signals (128 and above) as 'special' values as well (as I've seen some merge tools self destruct like that from time to time)

----- Original Message -----
From: gitster@pobox.com
To: john@keeping.me.uk
Cc: Tom Tanner (BLOOMBERG/ LONDON), davvid@gmail.com, git@vger.kernel.org
At: 08/14/16 04:21:18

John Keeping <john@keeping.me.uk> writes:

> At the moment difftool's "trust exit code" logic always suppresses the
> exit status of the diff utility we invoke.  This is useful because we
> don't want to exit just because diff returned "1" because the files
> differ, but it's confusing if the shell returns an error because the
> selected diff utility is not found.
>
> POSIX specifies 127 as the exit status for "command not found" and 126
> for "command found but is not executable" [1] and at least bash and dash
> follow this specification, while diff utilities generally use "1" for
> the exit status we want to ignore.
>
> Handle 126 and 127 as special values, assuming that they always mean
> that the command could not be executed.

Sounds like a reasonable thing to do.  Will queue; thanks.


             reply	other threads:[~2016-08-15 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 10:38 Tom Tanner (BLOOMBERG/ LONDON) [this message]
2016-08-15 20:21 ` [PATCH] difftool: always honor "command not found" exit code Junio C Hamano
2016-08-15 21:35   ` John Keeping
2016-08-15 21:54     ` [PATCH v2] difftool: always honor fatal error exit codes John Keeping
2016-08-15 22:26       ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2016-08-12  7:13 git difftool and git mergetool aren't returning errors when the tool has issues Tom Tanner (BLOOMBERG/ LONDON)
2016-08-13 10:36 ` John Keeping
2016-08-13 11:30   ` [PATCH] difftool: always honor "command not found" exit code John Keeping
2016-08-13 22:59     ` David Aguilar
2016-08-14  3:21     ` Junio C Hamano

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=57B19B9F0205070000390238_0_29566@p057 \
    --to=ttanner2@bloomberg.net \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=john@keeping.me.uk \
    /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