From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Aguilar <davvid@gmail.com>,
git@vger.kernel.org, charles@hashpling.org,
markus.heidelberg@web.de
Subject: [PATCH] Explain seemingly pointless use of system in difftool
Date: Thu, 23 Apr 2009 21:18:09 +0200 [thread overview]
Message-ID: <20090423191809.GC8433@blimp.localdomain> (raw)
In-Reply-To: <20090423190835.GB8433@blimp.localdomain>
Portability reasons.
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
---
Alex Riesen, Thu, Apr 23, 2009 21:08:35 +0200:
> Alex Riesen, Thu, Apr 23, 2009 20:57:32 +0200:
> > I'll add this comment regarding use of system in the case where exec
> > is right choice on all accounts and resend the patch:
> >
> > # ActiveState Perl for Win32 does not implement POSIX semantics of
> > # exec* system call. It just spawns the given executable and finishes
> > # the starting program, exiting with code 0.
> > # system will at least catch the errors in returned by git diff,
> > # allowing the caller of git difftool better handling of failures.
>
> Oh... I'm too late...
>
There.
git-difftool.perl | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/git-difftool.perl b/git-difftool.perl
index bd828c2..9255d23 100755
--- a/git-difftool.perl
+++ b/git-difftool.perl
@@ -82,5 +82,11 @@ sub generate_command
}
setup_environment();
+
+# ActiveState Perl for Win32 does not implement POSIX semantics of
+# exec* system call. It just spawns the given executable and finishes
+# the starting program, exiting with code 0.
+# system will at least catch the errors returned by git diff,
+# allowing the caller of git difftool better handling of failures.
my $rc = system(generate_command());
exit($rc | ($rc >> 8));
--
1.6.3.rc1.74.g42ff
prev parent reply other threads:[~2009-04-23 19:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 7:27 [PATCH] Wait for git diff to finish in git difftool Alex Riesen
2009-04-22 8:26 ` David Aguilar
2009-04-22 11:04 ` Alex Riesen
2009-04-22 18:59 ` Junio C Hamano
2009-04-22 20:40 ` Alex Riesen
2009-04-23 4:21 ` Junio C Hamano
2009-04-23 7:33 ` Alex Riesen
2009-04-23 8:26 ` Junio C Hamano
2009-04-23 9:52 ` Alex Riesen
2009-04-23 14:00 ` Sverre Rabbelier
2009-04-23 14:51 ` Junio C Hamano
2009-04-23 18:57 ` Alex Riesen
2009-04-23 19:08 ` Alex Riesen
2009-04-23 19:18 ` Alex Riesen [this message]
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=20090423191809.GC8433@blimp.localdomain \
--to=raa.lkml@gmail.com \
--cc=charles@hashpling.org \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=markus.heidelberg@web.de \
/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).