All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Robin Shen <robin@onedev.io>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
	"jgit-dev@eclipse.org" <jgit-dev@eclipse.org>
Subject: Re: Introducing OneDev - an open source git server with interesting features
Date: Thu, 10 Jan 2019 13:30:36 -0800	[thread overview]
Message-ID: <20190110213036.GC17382@google.com> (raw)
In-Reply-To: <SG2PR04MB320586447FF738E008C373FFB9840@SG2PR04MB3205.apcprd04.prod.outlook.com>

Robin Shen wrote:

> Yes it is using JGit for most operations. JGit API is very well
> designed and is a joy to use. The performance is very good, except
> for long operations such as full clone. So for pull/push I am
> calling native git, but for other operations which may need to be
> executed several times during a request I am using JGit which is
> much faster thanks for the in-process cache.
>
> I also filed several suggestions/bugs while using JGit:
>
> https://bugs.eclipse.org/bugs/buglist.cgi?email1=robin%40pmease.com&emailreporter1=1&emailtype1=substring&product=JGit&query_format=advanced

Thanks, that's very helpful.

[...]
> As to compared to other software listed here, I am only used GitHub
> intensively, so can not provide any valuable information.

No worries.  Thanks for indulging my questions. :)

Jonathan

      parent reply	other threads:[~2019-01-10 21:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 11:42 Introducing OneDev - an open source git server with interesting features Robin Shen
2019-01-07 22:26 ` Jonathan Nieder
     [not found]   ` <SG2PR04MB320586447FF738E008C373FFB9840@SG2PR04MB3205.apcprd04.prod.outlook.com>
2019-01-10  7:34     ` Robin Shen
2019-01-10 21:30     ` Jonathan Nieder [this message]

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=20190110213036.GC17382@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jgit-dev@eclipse.org \
    --cc=robin@onedev.io \
    /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.