From: Dennis Schridde <devurandom@gmx.net>
To: git@vger.kernel.org
Subject: Odd number of elements in anonymous hash
Date: Tue, 8 Jan 2008 17:38:56 +0100 [thread overview]
Message-ID: <200801081738.56624.devurandom@gmx.net> (raw)
Hello!
I am getting "Odd number of elements in anonymous hash at /usr/bin/git-svn
line 1760." (normal output, no warning/error) during git-svn-clone.
I am using git version 1.5.4.rc2.
Line 1760 is this (with context, marked with '!!'):
# see if we have it in our config, first:
eval {
my $section = "svn-remote.$self->{repo_id}";
!! $svnsync = {
url => tmp_config('--get', "$section.svnsync-url"),
uuid => tmp_config('--get', "$section.svnsync-uuid"),
}
};
The commandline was "git svn
clone --authors-file=/var/git/org.gna.warzone.git/authors --use-svnsync-props --stdlayout
file:///var/svn/warzone2100/ org.gna.warzone.git/"
I assume this is some kind of bug?
--Dennis
next reply other threads:[~2008-01-08 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 16:38 Dennis Schridde [this message]
2008-01-08 17:21 ` Odd number of elements in anonymous hash Junio C Hamano
2008-01-08 17:30 ` Dennis Schridde
2008-01-10 8:38 ` Eric Wong
2008-01-10 11:04 ` Dennis Schridde
2008-01-10 17:13 ` Dennis Schridde
2008-01-10 20:08 ` Junio C Hamano
2008-01-10 21:13 ` Dennis Schridde
2008-01-10 21:45 ` Junio C Hamano
2008-01-12 7:13 ` [PATCH] git-svn: handle leading/trailing whitespace from svnsync revprops Eric Wong
2008-01-12 7:57 ` Junio C Hamano
2008-01-12 9:12 ` Eric Wong
2008-01-12 9:55 ` Björn Steinbrink
2008-01-12 18:57 ` Junio C Hamano
2008-01-12 19:31 ` Junio C Hamano
2008-01-12 12:34 ` Dennis Schridde
2008-01-09 22:58 ` Odd number of elements in anonymous hash Eric Wong
[not found] ` <200801240037.33908.devurandom@gmx.net>
[not found] ` <4797E894.8060706@vilain.net>
[not found] ` <200801241513.45088.devurandom@gmx.net>
2008-01-24 23:10 ` Sam Vilain
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=200801081738.56624.devurandom@gmx.net \
--to=devurandom@gmx.net \
--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).