From: Junio C Hamano <gitster@pobox.com>
To: "Robert Newson" <robert.newson@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Perl warning in git-svn (git v1.5.3-rc7-16-ge340d7d)
Date: Fri, 31 Aug 2007 07:52:08 -0700 [thread overview]
Message-ID: <7vveav21uv.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <46aeb24f0708310558t2defc547v483586f116d8b8ac@mail.gmail.com> (Robert Newson's message of "Fri, 31 Aug 2007 13:58:43 +0100")
"Robert Newson" <robert.newson@gmail.com> writes:
> The latest head of git gives me this when doing most operations, this
> also happens with the rc7 experimental Debian package. It's annoying
> because it prints this line hundreds of times for each call to 'log',
> for example
>
> "Use of uninitialized value in string eq at blah/git/git-svn line 826."
>
> and this fixes it;
Curious. I wonder how can it trigger.
Presimably, that while (<$fh>) loop is reading from git-log, and
the first line would look like "commit [0-9a-f]{40}" and will
set $hash, do "next". Which means the variable should have been
initialized by the time the part that complains about string eq
(which I think is "if ($c && $c eq $hash)" comparison) is
reached.
next prev parent reply other threads:[~2007-08-31 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 12:58 Perl warning in git-svn (git v1.5.3-rc7-16-ge340d7d) Robert Newson
2007-08-31 14:52 ` Junio C Hamano [this message]
2007-08-31 15:21 ` Eric Wong
2007-08-31 15:31 ` Robert Newson
2007-08-31 16:09 ` Junio C Hamano
2007-08-31 16:18 ` Robert Newson
2007-08-31 16:25 ` Robert Newson
2007-08-31 16:25 ` Robert Newson
2007-08-31 20:50 ` Junio C Hamano
2007-08-31 21:22 ` Junio C Hamano
2007-08-31 23:47 ` Sam Vilain
2007-08-31 23:51 ` Johannes Schindelin
2007-08-31 21:29 ` git-svn: Protect against "diff.color = true" Junio C Hamano
2007-08-31 21:38 ` Johannes Schindelin
2007-08-31 21:46 ` Junio C Hamano
2007-08-31 21:53 ` Johannes Schindelin
2007-08-31 22:14 ` Junio C Hamano
2007-08-31 21:58 ` Eric Wong
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=7vveav21uv.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=robert.newson@gmail.com \
/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).