From: Thomas Adam <thomas@xteddy.org>
To: Jeremie Nikaes <jeremie.nikaes@ensimag.imag.fr>
Cc: git@vger.kernel.org, jrnieder@gmail.com,
"Arnaud Lacurie" <arnaud.lacurie@ensimag.imag.fr>,
"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 11:16:30 +0100 [thread overview]
Message-ID: <BANLkTik--BAqZxCYQ-ApUn2yKmcr_-hubg@mail.gmail.com> (raw)
In-Reply-To: <1307440754-3697-1-git-send-email-jeremie.nikaes@ensimag.imag.fr>
Hi,
On 7 June 2011 10:59, Jeremie Nikaes <jeremie.nikaes@ensimag.imag.fr> wrote:
> + @cmd = split(/ /,$entry);
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?
> + print STDERR "Unknown capability. Aborting...\n";
warn()?
> + print STDOUT "refspec refs/heads/*:refs/mediawiki/$remotename/*\n";
> + print STDOUT "import\n";
> + print STDOUT "list\n";
> + print STDOUT "option\n";
> + print STDOUT "push\n";
> + print STDOUT "\n";
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?
> + 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";
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.
-- Thomas Adam
next prev parent reply other threads:[~2011-06-07 10:16 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 [this message]
2011-06-07 11:20 ` Matthieu Moy
2011-06-07 11:33 ` Arnaud Lacurie
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=BANLkTik--BAqZxCYQ-ApUn2yKmcr_-hubg@mail.gmail.com \
--to=thomas@xteddy.org \
--cc=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 \
/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).