Il 02/09/2012 22:42, Junio C Hamano ha scritto:
Marco Stornelli <marco.stornelli@xxxxxxxxx> writes:
Il 01/09/2012 15:59, Johannes Sixt ha scritto:
Look how you write:
perl -e '... $ENV{'PATCHTMP'} ...'
That is, perl actually sees this script:
... $ENV{PATCHTMP} ...
(no quotes around PATCHTMP). That my be perfectly valid perl, but is not
what you intended.
I don't understand what you mean when you say "is not what you
intended"...
When you wrote this:
CCS=`perl -e 'local $/=undef; open FILE, $ENV{'PATCHTMP'};...
which one of the following did you mean to feed Perl?
(1) open FILE, $ENV{'PATCHTMP'};
(2) open FILE, $ENV{PATCHTMP};
The patch text makes it look as if you wanted to do (1), but what is
fed to perl is (2), as Johannes points out.
Saying:
CCS=`perl -e 'local $/=undef; open FILE, $ENV{PATCHTMP};...
would have been more natural if you really meant to do (2), don't
you think? So what you wrote is at least misleading.
But I think I agree with Johannes's rewrite of the loop, so this may
be a moot point.
I tried the Johannes's script, but it seems it doesn't work well with
the pattern of format-patch (To: <mail1>,\n <mail2>,\n <mailN>).
The multilines are not well managed. I can change my script to double
quotas (I think perl and regexp are much more powerful rather than the
while loop though it can be less readable), if it's not ok, I let other
git shell expert to adjust the script. I hope this thread it will be
useful for others.
Marco
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html