Re: Reading commit objects

4 messages, 4 authors, 2016-06-15 · open the first message on its own page

Re: Reading commit objects

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:57:24

Chico Sokol [off-list ref] writes:
Ok, we discovered that the commit object actually contains the tree
object's sha1, by reading its contents with python zlib library.

So the bug must be with our java code (we're building a java lib).
Why aren't you using jgit?

Re: Reading commit objects

From: Chico Sokol <hidden>
Date: 2016-06-15 22:57:24

It was git who created that object.

We're trying to build a improved java library focused in our needs
(jgit has a really confusing api focused in solving egit needs). But
we're about to get into their code to discover how to decompress git
objects.


--
Chico Sokol


On Tue, May 21, 2013 at 7:22 PM, Junio C Hamano [off-list ref] wrote:
Chico Sokol [off-list ref] writes:
quoted
Ok, we discovered that the commit object actually contains the tree
object's sha1, by reading its contents with python zlib library.

So the bug must be with our java code (we're building a java lib).
Why aren't you using jgit?

Re: Reading commit objects

From: Jonathan Nieder <hidden>
Date: 2016-06-15 22:57:24

Chico Sokol wrote:
We're trying to build a improved java library focused in our needs
(jgit has a really confusing api focused in solving egit needs).
JGit is also open to contributions, including contributions that
add less confusing API calls. :)  See

 http://wiki.eclipse.org/JGit/User_Guide
 http://wiki.eclipse.org/EGit/Contributor_Guide#JGit
 http://wiki.eclipse.org/EGit/Contributor_Guide#Using_Gerrit_at_https:.2F.2Fgit.eclipse.org.2Fr
 https://dev.eclipse.org/mailman/listinfo/jgit-dev

Thanks,
Jonathan

Re: Reading commit objects

From: Shawn Pearce <hidden>
Date: 2016-06-15 22:57:24

On Tue, May 21, 2013 at 3:33 PM, Chico Sokol [off-list ref] wrote:
It was git who created that object.

We're trying to build a improved java library focused in our needs
(jgit has a really confusing api focused in solving egit needs).
JGit code... is confusing because its fast. We spent a lot of time
trying to make things fast on the JVM, and somewhat comparable with C
Git even though its not in C. Some of the low-level APIs are fast
because they bypass conventional Java wisdom and just tell the #@!*
machine what to do, with no pretty bits about it. Make it pretty, it
goes slower. Or uses more RAM. Java likes RAM.

Good luck making an improved library. JGit of course is also
interested in contributions. The api package has been trying to make a
simpler calling convention for common use cases that match the command
line interface user are familiar with, but its still incomplete and
hides some optimizations that are possible with the lower-level calls.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help