From: David Aguilar <davvid@gmail.com>
To: Alex Riesen <raa.lkml@gmail.com>, gitster@poxbox.com
Cc: git@vger.kernel.org, charles@hashpling.org, markus.heidelberg@web.de
Subject: Re: [PATCH] Wait for git diff to finish in git difftool
Date: Wed, 22 Apr 2009 01:26:54 -0700 [thread overview]
Message-ID: <20090422082652.GA32698@gmail.com> (raw)
In-Reply-To: <81b0412b0904220027t7afd1ed7xc57c479ef8cdb6b9@mail.gmail.com>
On 0, Alex Riesen <raa.lkml@gmail.com> wrote:
> In ActivetState Perl, exec does not wait for the started program. This
> breaks difftool tests and may cause unexpected behaviour: git difftool
> has returned, but the rest of code (diff and possibly the interactive
> program are still running in the background.
Thanks for keeping an eye on portability.
There's a tiny typo in the commit message (Active't'State) that
maybe you can tweak before applying? ('you' being Junio)
For whatever it's worth,
Acked-by: David Aguilar <davvid@gmail.com>
> I usually don't care for exit code in a pure UI tool, so the kill signal
> is just ORed together with the real exit code just to provide indication
> of error.
This seems reasonable. The exit code isn't very important in
the common 'show-me-the-diff' read-only scenario, and I wouldn't
expect anyone to rely on difftool being exactly exit-code
equivalent to git-diff.
> diff --git a/git-difftool.perl b/git-difftool.perl
> index 948ff7f..bd828c2 100755
> --- a/git-difftool.perl
> +++ b/git-difftool.perl
> @@ -82,4 +82,5 @@ sub generate_command
> }
>
> setup_environment();
> -exec(generate_command());
> +my $rc = system(generate_command());
> +exit($rc | ($rc >> 8));
> --
> 1.6.3.rc0.45.g63634
--
David
next prev parent reply other threads:[~2009-04-22 8:29 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 [this message]
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 ` [PATCH] Explain seemingly pointless use of system in difftool 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=20090422082652.GA32698@gmail.com \
--to=davvid@gmail.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=gitster@poxbox.com \
--cc=markus.heidelberg@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.