From: Junio C Hamano <junkio@cox.net>
To: Inaki Arenaza <iarenuno@eteo.mondragon.edu>
Cc: git@vger.kernel.org, Martin Langhoff <martin@catalyst.net.nz>
Subject: Re: [PATCH] git-cvsimport: add suport for CVS pserver method HTTP/1.x proxying
Date: Thu, 23 Nov 2006 14:01:37 -0800 [thread overview]
Message-ID: <7v64d5keke.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <11642344172790-git-send-email-iarenuno@eteo.mondragon.edu> (Inaki Arenaza's message of "Wed, 22 Nov 2006 23:26:57 +0100")
Thanks. The patch looks very sane, isolated to be safe enough,
and useful.
Except that this statement made me go "huh?" wondering what it
would do to the $filehandle to evaluate <$filehandle> in a void
context:
+ # Skip the empty line of the proxy server output
+ <$s>;
and I ended up looking in perlop.pod and came up empty.
The "I/O Operators" section talks about evaluating <$s> in a
scalar context (i.e. "$rep = <$s>"), which we all know would
return a single line, and in list context, which swallows
everything up to EOF, an obvious disaster for this particular
use. I couldn't find how it is defined to behave in a void
context. By experiments I know this returns only one line, but
it leaves me feeling somewhat uneasy.
Also it has a style inconsistency between "if(expression) {" and
"if(expression){", and I do not like either of them, but fixing
that should be left to a separate patch.
I'll apply this unless Martin or other people on the list who
have stake in cvsimport objects.
next prev parent reply other threads:[~2006-11-23 22:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 22:26 [PATCH] git-cvsimport: add suport for CVS pserver method HTTP/1.x proxying Inaki Arenaza
[not found] ` <7v64 d5keke.fsf@assigned-by-dhcp.cox.net>
2006-11-23 22:01 ` Junio C Hamano [this message]
2006-11-23 22:09 ` Martin Langhoff (CatalystIT)
2006-11-23 23:02 ` Junio C Hamano
2006-11-23 23:20 ` Martin Langhoff (CatalystIT)
2006-11-23 23:52 ` Martin Langhoff
2006-11-24 0:24 ` Junio C Hamano
2006-11-25 12:43 ` Ignacio Arenaza
2006-11-24 1:42 ` Jeff King
2006-11-24 2:54 ` Junio C Hamano
2006-11-24 8:43 ` Ignacio Arenaza
2006-11-24 8:46 ` Ignacio Arenaza
2006-11-24 8:57 ` Junio C Hamano
2006-11-24 9:05 ` Ignacio Arenaza
2006-11-24 11:48 ` Junio C Hamano
2006-11-27 16:27 ` Ignacio Arenaza
2006-11-24 14:57 ` Jeff King
2006-11-24 4:48 ` Christian Couder
2006-11-24 8:41 ` Ignacio Arenaza
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=7v64d5keke.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=iarenuno@eteo.mondragon.edu \
--cc=martin@catalyst.net.nz \
/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.