Add cc to git@xxxxxxxxxxxxxxx and jgit-dev@xxxxxxxxxxx ======================================================== From: Robin Shen Sent: Thursday, January 10, 2019 2:37 PM To: Jonathan Nieder Cc: git@xxxxxxxxxxxxxxx; jgit-dev@xxxxxxxxxxx Subject: Re: Introducing OneDev - an open source git server with interesting features Hi Jonathan, 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 I'd like to help fixing, but right now does not have time to dig into JGit internals... As to compared to other software listed here, I am only used GitHub intensively, so can not provide any valuable information. Regards Robin From: Jonathan Nieder <jrnieder@xxxxxxxxx> Sent: Tuesday, January 8, 2019 6:26:31 AM To: Robin Shen Cc: git@xxxxxxxxxxxxxxx; jgit-dev@xxxxxxxxxxx Subject: Re: Introducing OneDev - an open source git server with interesting features +jgit-dev Hi Robin, Robin Shen wrote: > Dear git users, > > OneDev is an open source git server with interesting features such > as language aware code search/navigation, issue workflow > customization, free source/diff comment and discussion, etc. > > It is using MIT license and hope it can be useful to someone. Learn > more at https://onedev.io Thanks for writing! Looking at https://github.com/theonedev/onedev/blob/master/core/pom.xml, it appears this is a web interface that uses JGit for Git support. Can you say a little about how it compares to Gitblit <http://gitblit.com>, Phabricator, Gerrit, and other interfaces? Also, if you have time for it, mind saying a little about what your experience using JGit has been like? Any thoughts about what worked well and what didn't work as well? This can help both the Git and JGit projects: - Git, since it can help us learn from JGit's successes and mistakes - JGit, since it's not too late to make the API better :) Sincerely, Jonathan
