From: Andreas Schwab <schwab@linux-m68k.org>
To: Nathaniel W Filardo <nwf@cs.jhu.edu>
Cc: git@vger.kernel.org
Subject: Re: Endianness bug in git-svn or called component?
Date: Fri, 04 Dec 2009 21:16:40 +0100 [thread overview]
Message-ID: <m23a3qa40n.fsf@igel.home> (raw)
In-Reply-To: <20091204174458.GV17192@gradx.cs.jhu.edu> (Nathaniel W. Filardo's message of "Fri, 4 Dec 2009 12:44:58 -0500")
Nathaniel W Filardo <nwf@cs.jhu.edu> writes:
> On this machine,
>
> mirrors hydra:/tank0/mirrors/misc% uname -a
> FreeBSD hydra.priv.oc.ietfng.org 9.0-CURRENT FreeBSD 9.0-CURRENT #13: Sat Nov 14 19:40:25 EST 2009 root@hydra.priv.oc.ietfng.org:/systank/obj/systank/src/sys/NWFKERN sparc64
>
> attempting to fetch from an svn source yields the following error:
>
> rs hydra:/tank0/mirrors/misc% git svn init -s https://joshua.svn.sourceforge.net/svnroot/joshua test-joshua
> Initialized empty Git repository in /tank0/mirrors/misc/test-joshua/.git/
> mirrors hydra:/tank0/mirrors/misc% cd test-joshua
> mirrors hydra:/tank0/mirrors/misc/test-joshua% git svn fetch
> A scripts/distributedLM/config.template
> [...]
> A build.xml
> r1 = fe84a7d821ec6d92da75133ac7ad1deb476b6484 (refs/remotes/trunk)
> error: index uses extension, which we do not understand
> fatal: index file corrupt
> write-tree: command returned error: 128
I could not reproduce that on powerpc (both 32bit and 64bit).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-12-04 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 17:44 Endianness bug in git-svn or called component? Nathaniel W Filardo
2009-12-04 20:16 ` Andreas Schwab [this message]
2009-12-04 20:29 ` Nathaniel W Filardo
2009-12-18 9:05 ` Nathaniel W Filardo
2009-12-27 6:11 ` [RESEND] [PATCH] Endianness bug in index cache logic Nathaniel W Filardo
2009-12-27 12:39 ` Erik Faye-Lund
2009-12-27 16:12 ` Nathaniel W Filardo
2009-12-27 18:24 ` Junio C Hamano
2009-12-27 19:12 ` Tomas Carnecky
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m23a3qa40n.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=nwf@cs.jhu.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).