All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Imran M Yousuf <imyousuf@gmail.com>,
	Carlos Rica <jasampler@gmail.com>,
	git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: GSoC 2008 - Mentors Wanted!
Date: Thu, 6 Mar 2008 21:48:01 +0100	[thread overview]
Message-ID: <200803062148.01596.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <20080306050846.GQ8410@spearce.org>

Den Thursday 06 March 2008 06.08.46 skrev Shawn O. Pearce:
> Robin Rosenberg <robin.rosenberg@dewire.com> wrote:
> > You will find support in jgit for this today. Cloning over git and ssh
> > real soon. I'm clensing the oopses from the history right now. (bless
> > rebase -i and git-gui).
>
> I'm sort of waiting to see this fetch history soon.  :-)
>
> The reason is I just got index v2 support (runtime read side) completed
> and I want to add index v2 generation to IndexPack.  I also want to start
> building a PackWriter so we can work on native transport push over SSH.
>
> If we get fetch/push running I think we are heading into the area
> where it is of some real use to people.
>
> > There might be some operations that might be harder to do well in Java.
> > For those exec'ing might be the solution, I'm thinking repack, but then I
> > haven't tried it yet.
>
> I'm determined to even get "proper" packfile generation in Java.
> But it may be time consuming to build.  There may be license issues
> around doing a direct cribbed port of the delta generation.  :-\

If you know where to look, you might find a version of it. :) I don't think
I've changed so much as to prevent you from starting to code the push
part.

> > If someone *did* make a fully reentrant libgit, I'd be inclined to
> > balance my opinions differently.
>
> Really?  If jgit is basically as fast as C git, but doesn't have
> the overheads of dropping in and out of JNI or fork/exec then you
> can actually get pretty good performance out of a Java application.
I meant "might be".  :]

-- robin



  parent reply	other threads:[~2008-03-06 20:48 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04  5:11 GSoC 2008 - Mentors Wanted! Shawn O. Pearce
2008-03-04  9:23 ` Matthieu Moy
2008-03-05  6:06   ` Shawn O. Pearce
2008-03-04 17:14 ` Jakub Narebski
2008-03-04 20:47 ` Carlos Rica
2008-03-04 20:51   ` Carlos Rica
2008-03-05  5:36   ` Shawn O. Pearce
2008-03-05  7:58     ` Imran M Yousuf
2008-03-05  8:15       ` Shawn O. Pearce
2008-03-05  8:25         ` Imran M Yousuf
2008-03-05  8:33           ` Imran M Yousuf
2008-03-05 14:55           ` Noel Grandin
2008-03-05 16:37             ` Johannes Schindelin
2008-03-06  4:58             ` Shawn O. Pearce
2008-03-05 21:13       ` Robin Rosenberg
2008-03-06  5:08         ` Shawn O. Pearce
2008-03-06  5:19           ` Imran M Yousuf
2008-03-06 11:04           ` Johannes Schindelin
2008-03-06 20:48           ` Robin Rosenberg [this message]
2008-03-06  5:33         ` Imran M Yousuf
2008-03-06 20:47           ` Robin Rosenberg
2008-03-06  5:06 ` Christian Couder
2008-03-06  5:31   ` Christian Couder
2008-03-06  6:44     ` Shawn O. Pearce

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=200803062148.01596.robin.rosenberg@dewire.com \
    --to=robin.rosenberg@dewire.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=imyousuf@gmail.com \
    --cc=jasampler@gmail.com \
    --cc=spearce@spearce.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.