Robin Rosenberg <robin.rosenberg.lists@xxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html