From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Cc: Robin Rosenberg <robin.rosenberg@dewire.com>
Subject: [ANNOUNCE] EGit and JGit projects have split
Date: Wed, 17 Jun 2009 08:06:57 -0700 [thread overview]
Message-ID: <20090617150657.GF11191@spearce.org> (raw)
The EGit and JGit projects have now split apart. Up until today
they were housed in the same repository at repo.or.cz.
As EGit is moving to the Eclipse Foundation umbrella, we wanted to
fully split JGit off such that applications trying to make use of
JGit can do so without dragging in the EGit specific code.
JGit is now here:
http://repo.or.cz/w/jgit.git
git://repo.or.cz/jgit.git
direct patches to git ML
same maintainers (myself, Robin Rosenberg)
EGit is still in the same location:
http://repo.or.cz/w/egit.git
git://repo.or.cz/egit.git
direct patches to egit-dev@eclipse.org
same maintainers (myself, Robin Rosenberg)
FYI, no history was rewritten. Two commits were introduced to
create the fork:
JGit: 9171327f92240a3dbef4a389a2a6378044013803 (rm -rf *egit*)
EGit: 8f4475f4324599ab704eb1dc3adec92d3b1b85df (rm -rf *jgit*)
Please update your personal forks and clones as necessary.
--
Shawn.
reply other threads:[~2009-06-17 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090617150657.GF11191@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@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.
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 NNTP newsgroup(s).