From: dclist@gmail.com
To: git@vger.kernel.org
Subject: git-svn fails when svn.noMetaData is set
Date: Mon, 06 Dec 2010 21:24:27 -0500 [thread overview]
Message-ID: <87bp4ytj50.fsf@invalid.clx> (raw)
Run on git version 1.7.3. Analyzed the source code using commit
0b0cd0e0a2.
Steps to reproduce
------------------
1. Set svn.noMetaData to true globally.
2. Invoke git svn clone on an svn repository
What happens
------------
Fatal error: "Not a SCALAR reference at /usr/lib/git-core/git-svn line 1457"
What I expect to happen
-----------------------
The clone to complete successfully
Analysis
--------
The problem seems to be line 1457, where the variable 'v' is
dereferenced and assigned a value --- $$v = $tmp ---- in combination
with line 118, where the value of the variable 'v' for the option
no-metadata is specified as a subroutine and, therefore, cannot be
assigned a value in the manner defined on line 1457. I believe the same
is true of other options that specify subroutines as their hash values.
reply other threads:[~2010-12-07 2:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87bp4ytj50.fsf@invalid.clx \
--to=dclist@gmail.com \
--cc=git@vger.kernel.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).