From: Stefan Sperling <stsp@elego.de>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org, subversion@elego.de
Subject: Re: [PATCH] Allow multiple tag and branch directories in git-svnimport
Date: Wed, 22 Aug 2007 12:24:15 +0200 [thread overview]
Message-ID: <20070822102415.GA24305@jack.stsp.lan> (raw)
In-Reply-To: <86wsvook5s.fsf@blue.stonehenge.com>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
On Tue, Aug 21, 2007 at 10:46:23AM -0700, Randal L. Schwartz wrote:
> Stefan> Ouch, just noticed it's a bad idea to try to initialise
> Stefan> an array with a scalar. Sorry :-/
>
> That's completely normal. Perl predictably promotes the single scalar to an
> array of one element. I wouldn't have even noticed it in a detailed code
> review, since it's so normal to do that.
>
> In fact, the parens that you added do *not* make it a list. The parens
> are purely for precedence
> So, your parens are not only uncommon, they are also completely ineffective,
> similar to replacing 2 + 3 with (2) + (3) :)
Thanks for clarifying. Prior to hacking on git-svnimport
my perl "skills" (if any) were strictly read-only.
So I'm quite a noob wrt perl.
Feel free to nit the patch further :)
--
Stefan Sperling <stsp@elego.de> Software Developer
elego Software Solutions GmbH HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12 Tel: +49 30 23 45 86 96
13355 Berlin Fax: +49 30 23 45 86 95
http://www.elego.de Geschaeftsfuehrer: Olaf Wagner
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
prev parent reply other threads:[~2007-08-22 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 17:08 [PATCH] Allow multiple tag and branch directories in git-svnimport Stefan Sperling
2007-08-21 17:38 ` Stefan Sperling
2007-08-21 17:46 ` Randal L. Schwartz
2007-08-22 10:24 ` Stefan Sperling [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=20070822102415.GA24305@jack.stsp.lan \
--to=stsp@elego.de \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=subversion@elego.de \
/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).