From: madmarcos <fru574@my.utsa.edu>
To: git@vger.kernel.org
Subject: Re: Java Inflater problem decompressing packfile
Date: Sat, 16 Apr 2011 21:06:15 -0700 (PDT) [thread overview]
Message-ID: <1303013175664-6280295.post@n2.nabble.com> (raw)
In-Reply-To: <1303012970295-6280285.post@n2.nabble.com>
I hit send too quickly.
beneath the readFile call in the test4() method are several commented-out
System.arraycopy lines. you can uncomment any one of them to see the blob or
tree decompressed. all but the the last arraycopy line work fine. the last
one is the problem.
thanks for any light you can shed on the problem. I am pulling my hair out.
--
View this message in context: http://git.661346.n2.nabble.com/Java-Inflater-problem-decompressing-packfile-tp6278154p6280295.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2011-04-17 4:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 2:05 Java Inflater problem decompressing packfile madmarcos
2011-04-16 6:37 ` Jeff King
2011-04-16 14:23 ` madmarcos
2011-04-16 14:36 ` madmarcos
2011-04-16 14:58 ` madmarcos
2011-04-16 15:50 ` madmarcos
2011-04-17 0:40 ` madmarcos
2011-04-17 4:02 ` madmarcos
2011-04-17 4:06 ` madmarcos [this message]
2011-04-17 4:36 ` Jeff King
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=1303013175664-6280295.post@n2.nabble.com \
--to=fru574@my.utsa.edu \
--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).