From: Tim Henigan <tim.henigan@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: gitster@pobox.com, davvid@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH 7/9] difftool: teach difftool to handle directory diffs
Date: Sat, 17 Mar 2012 20:58:12 -0400 [thread overview]
Message-ID: <CAFouetg1JEBsO4SyHxpaphQZQtmbo8ugbHoUWnhSXku4DWuvVA@mail.gmail.com> (raw)
In-Reply-To: <m3fwd7l2mu.fsf@localhost.localdomain>
On Sat, Mar 17, 2012 at 10:32 AM, Jakub Narebski <jnareb@gmail.com> wrote:
> Tim Henigan <tim.henigan@gmail.com> writes:
>
>> + foreach my $path (keys %submodule) {
>> + if (defined $submodule{$path}{left}) {
>> + open(SUBMOD, ">$ldir/$path") or die $!;
>> + print(SUBMOD "Subproject commit $submodule{$path}{left}");
>> + close(SUBMOD);
>> + }
>> + if (defined $submodule{$path}{right}) {
>> + open(SUBMOD, ">$rdir/$path") or die $!;
>> + print(SUBMOD "Subproject commit $submodule{$path}{right}");
>> + close(SUBMOD);
>
> Could you please use modern Perl, and use lexical filehandles instead
> of globs, and 3-arg version of 'open', i.e.
>
> + open my $submod_fh, ">", "$ldir/$path" or die $!;
> + print $submod_fh "Subproject commit $submodule{$path}{left}";
> + close $submod_fh;
I will make this change in v2. Thank you for the review and the reminder.
>> +if (defined($dirdiff)) {
>> + my ($a, $b) = setup_dir_diff();
>> + if (defined($extcmd)) {
>> + system("$extcmd $a $b");
>> + } else {
>> + $ENV{GIT_DIFFTOOL_DIRDIFF} = 'true';
>> + system("git difftool--helper $a $b");
>> + }
>
> Why you use 'system' (and not in list form which does not require
> escaping shell characters) instead of git_cmd_try for first
> "git difftool--helper" invocation?
There is no good reason to use 'system' here. I will change this to
'Git::command_noisy' in v2.
> Is $extcmd and resultof setup_dir_diff() to be treated as shell
> snippet, and used in string form of 'system' without escaping shell
> metacharacters (like ' ' in filename)?
In v2, I will change to the list form of 'system' for the call to
$extcmd. I think I made some bad assumptions about the contents of
$extcmd, $a and $b because of my local test setup. However, changing
to list form should correct the oversight.
next prev parent reply other threads:[~2012-03-18 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 1:59 [PATCH 7/9] difftool: teach difftool to handle directory diffs Tim Henigan
2012-03-17 3:08 ` David Aguilar
2012-03-17 14:18 ` Tim Henigan
2012-03-17 14:32 ` Jakub Narebski
2012-03-18 0:58 ` Tim Henigan [this message]
2012-03-20 17:43 ` Tim Henigan
2012-03-20 18:35 ` Junio C Hamano
2012-03-20 20:17 ` Tim Henigan
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=CAFouetg1JEBsO4SyHxpaphQZQtmbo8ugbHoUWnhSXku4DWuvVA@mail.gmail.com \
--to=tim.henigan@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@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 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).