From: "Martin Langhoff (CatalystIT)" <martin@catalyst.net.nz>
To: Junio C Hamano <junkio@cox.net>
Cc: Inaki Arenaza <iarenuno@eteo.mondragon.edu>, git@vger.kernel.org
Subject: Re: [PATCH] git-cvsimport: add suport for CVS pserver method HTTP/1.x proxying
Date: Fri, 24 Nov 2006 11:09:58 +1300 [thread overview]
Message-ID: <45661C36.9010101@catalyst.net.nz> (raw)
In-Reply-To: <7v64d5keke.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> 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>;
It's a perl idiom that will discard one line of the $filehandle. If we
are 200% certain that it is empty, then it's fine. OTOH, it may well be
a bug in the particular proxy implementation Iñaki is using -- I don't
know enough about CVS proxying to tell.
> 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
This is in scalar context, and that's safe to rely on. Whether it is
clear enough in this non-Perl-native project... is a good flamewar
waiting to happen :-)
cheers,
martin
--
-----------------------------------------------------------------------
Martin @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington
WEB: http://catalyst.net.nz/ PHYS: Level 2, 150-154 Willis St
OFFICE: +64(4)916-7224 MOB: +64(21)364-017
Make things as simple as possible, but no simpler - Einstein
next prev parent reply other threads:[~2006-11-23 22:10 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
2006-11-23 22:09 ` Martin Langhoff (CatalystIT) [this message]
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=45661C36.9010101@catalyst.net.nz \
--to=martin@catalyst.net.nz \
--cc=git@vger.kernel.org \
--cc=iarenuno@eteo.mondragon.edu \
--cc=junkio@cox.net \
/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).