From: Shawn Pearce <spearce@spearce.org>
To: Chico Sokol <chico.sokol@gmail.com>
Cc: John Szakmeister <john@szakmeister.net>, git <git@vger.kernel.org>
Subject: Re: Reading commit objects
Date: Wed, 22 May 2013 13:02:06 -0700 [thread overview]
Message-ID: <CAJo=hJuO23YGMJV69WvdKweW7EYCYVE-f93w5a=+N2_xh_e1+A@mail.gmail.com> (raw)
In-Reply-To: <CABx5MBS9YgNmZD_tumMJ-MJVjHbRFCKbCjs9AZ347-OCwqO7qQ@mail.gmail.com>
On Wed, May 22, 2013 at 7:20 AM, Chico Sokol <chico.sokol@gmail.com> wrote:
> I'm not criticizing JGit, guys. It simply doesn't fit into our needs.
> We're not interested in mapping git commands in java and don't have
> the same RAM limitations.
I guess you aren't trying to process the WebKit or Linux kernel
repositories. Or you can afford more RAM than I can[1]. :-)
[1] $DAY_JOB has lots of RAM. Lots.
> Are you guys contributors of JGit?
Not really. I had nothing to do with JGit. :-)
> Can you guys point me out to the
> code that unpacks git objects? The closest I could get was that class:
> https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit/src/org/eclipse/jgit/internal/storage/file/UnpackedObject.java
This class handles the loose object format in $GIT_DIR/objects, but
does not handle objects contained in pack files. That is elsewhere,
and well, more complex. Look at PackFile.java.
> It seems to be a standard and a non standard format of the packed
> object, as I read the comments of this method:
> https://github.com/eclipse/jgit/blob/master/org.eclipse.jgit/src/org/eclipse/jgit/internal/storage/file/UnpackedObject.java#L272
There are two formats, the official format that is used, and an
experimental format that was discarded but is still supported for
legacy reasons.
> I suspect that the default inflater class of java api expect the
> object to be in the standard format.
>
> What the following comment mean? What's the "Experimental pack-based"
> format? Is there any docs on the specs of that?
Read the code. This is the dead format that is no longer written, but
is still supported.
next prev parent reply other threads:[~2013-05-22 20:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 21:21 Reading commit objects Chico Sokol
2013-05-21 21:25 ` Felipe Contreras
2013-05-21 21:37 ` John Szakmeister
2013-05-21 22:18 ` Chico Sokol
2013-05-21 22:22 ` Junio C Hamano
2013-05-21 22:33 ` Chico Sokol
2013-05-21 23:34 ` Jonathan Nieder
2013-05-22 5:54 ` Shawn Pearce
2013-05-22 4:51 ` java zlib woes (was: Reading commit objects) Andreas Krey
2013-05-22 5:56 ` Shawn Pearce
2013-05-27 4:11 ` Andreas Krey
2013-06-04 10:18 ` fetch delta resolution vs. checkout (was: java zlib woes) Andreas Krey
2013-05-22 5:59 ` Reading commit objects Shawn Pearce
2013-05-22 14:20 ` Chico Sokol
2013-05-22 20:02 ` Shawn Pearce [this message]
2013-05-22 14:25 ` Chico Sokol
2013-05-22 14:47 ` Chico Sokol
2013-05-22 19:59 ` Shawn Pearce
2013-05-21 22:20 ` Junio C Hamano
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='CAJo=hJuO23YGMJV69WvdKweW7EYCYVE-f93w5a=+N2_xh_e1+A@mail.gmail.com' \
--to=spearce@spearce.org \
--cc=chico.sokol@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@szakmeister.net \
/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).