From: Arnaud Lacurie <arnaud.lacurie@ensimag.imag.fr>
To: Thomas Adam <thomas@xteddy.org>
Cc: "Jeremie Nikaes" <jeremie.nikaes@ensimag.imag.fr>,
git@vger.kernel.org, jrnieder@gmail.com,
"Claire Fousse" <claire.fousse@ensimag.imag.fr>,
"David Amouyal" <david.amouyal@ensimag.imag.fr>,
"Matthieu Moy" <matthieu.moy@grenoble-inp.fr>,
"Sylvain Boulmé" <sylvain.boulme@imag.fr>
Subject: Re: [PATCHv2] Add a remote helper to interact with mediawiki, pull & clone handled
Date: Tue, 7 Jun 2011 13:33:09 +0200 [thread overview]
Message-ID: <BANLkTimTAhi6MZg_COopdyHwNifqmRVy0A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik--BAqZxCYQ-ApUn2yKmcr_-hubg@mail.gmail.com>
Hi,
2011/6/7 Thomas Adam <thomas@xteddy.org>:
> Hmm. What guarantees can you make about the scalar value of @cmd here
> once the split has happened? Do you not care, or do you have a
> hard-limit for split to use?
The verifications on the different cmd[x] are made in the few lines
"if ... elsif... elsif ... else" right after the split.
> These explicit calls to "STDOUT" here -- why? It's redundant typing
> and unsightly, and certainly not very perl-y. Is there some reason
> why you're using this style?
We wanted to highlight the fact that we are sending those lines to STDOUT
which is piped into the caller of the remote helper.
>
>> + print STDOUT "? refs/heads/master\n";
>> + print STDOUT '@'."refs/heads/master HEAD\n";
>> + print STDOUT "\n";
>
> Hmm. Why not just:
>
> print STDOUT '@'."refs/heads/master HEAD\n\n";
Here, we wanted to stick to the convention given by the remote-helper
documentation that indicates the list command should end with a blank line.
>
> There's certainly a large number of perl-specific clean-ups I'd be
> inclined to do -- and if I get time later, I might show you how. But
> don't let this necessarily put off this patch for inclusion or
> anything like that.
As said in previous mails, we are relatively new using perl (it's been
roughly two weeks)
so any advice on how to get things more perl-ish are welcome.
Thanks for your feedback
--
Arnaud Lacurie
prev parent reply other threads:[~2011-06-07 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 9:59 [PATCHv2] Add a remote helper to interact with mediawiki, pull & clone handled Jeremie Nikaes
2011-06-07 10:16 ` Thomas Adam
2011-06-07 11:20 ` Matthieu Moy
2011-06-07 11:33 ` Arnaud Lacurie [this message]
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=BANLkTimTAhi6MZg_COopdyHwNifqmRVy0A@mail.gmail.com \
--to=arnaud.lacurie@ensimag.imag.fr \
--cc=claire.fousse@ensimag.imag.fr \
--cc=david.amouyal@ensimag.imag.fr \
--cc=git@vger.kernel.org \
--cc=jeremie.nikaes@ensimag.imag.fr \
--cc=jrnieder@gmail.com \
--cc=matthieu.moy@grenoble-inp.fr \
--cc=sylvain.boulme@imag.fr \
--cc=thomas@xteddy.org \
/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).