git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: The EGIT Chronicles Issue Volume 3, Issue 1
Date: Mon, 6 Apr 2009 08:03:48 -0700	[thread overview]
Message-ID: <20090406150348.GH23604@spearce.org> (raw)
In-Reply-To: <200904060833.27711.robin.rosenberg.lists@dewire.com>

Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
>
> Most interestingly, some Eclipse developers, i.e. the ones
> that build and contribute to the Eclipse platform, have raised
> interest in Git for source control. We have had an Eclipse
> proposal under development for a while and finally submitted
> EGit for consideration as and Eclipse Technology project.  Link:
> http://www.eclipse.org/proposals/egit/
> 
> Egit is EPL and BSD licensed which license-wise qualifies it for
> inclusion into the Eclipse project, unlike the nearest competitor
> Mercurial that cannot be bundled with Eclipse due to the GPL.

For pretty much this reason alone, Eclipse is starting to consider
switching from CVS and SVN to Git.  Some committers were interested
in a switch to Mecurial, but the GPL license makes it unfriendly
to the project's distribution rules.

> - Shawn's been working on Gerrit2, a code review system built on
> top of JGit, the core of the Eclipse plugin.

Its also sucking up all of my time.

But... its open source, and is gaining (some) momentum in Git
communities that want mandatory code review, but who also want to
avoid the bottleneck of a maintainer / "merge monkey".

Junio made some remark back when I joined Google that Google just
swallows up open source developers whole, and you never hear from
them again.  At least half true.  Fortunately I am at least able to
open source (EPL if in EGit, BSD if in JGit, else APLv2) everything
that I do while in that big black hole known as Google.

> - Lots of stuff is coming. For example, a few diff engines are
> being considered, a blame implementation has been demonstrated,
> though not fully ready yet. Some simple merge/cherry picking
> capability is included already, but without the diff/patch engine
> it's not as fully automated as one might want yet. Gerrit2 uses
> it though.

The lack of a diff engine is starting to become an issue for me
in Gerrit2.  Maybe next month I'll be able to get to it, if someone
doesn't beat me to it first.  Gerrit2 users are asking for proper
cherry pick support, not just the path-level-only cr*p we do now.

-- 
Shawn.

      reply	other threads:[~2009-04-06 15:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  6:33 The EGIT Chronicles Issue Volume 3, Issue 1 Robin Rosenberg
2009-04-06 15:03 ` Shawn O. Pearce [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

  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=20090406150348.GH23604@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=robin.rosenberg.lists@dewire.com \
    /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).