From: Semen Vadishev <semen.vadishev@tmatesoft.com>
To: jgit-dev <jgit-dev@eclipse.org>,
EGit developer discussion <egit-dev@eclipse.org>,
Git Mailing List <git@vger.kernel.org>
Subject: [ANN] SubGit Early Access Program Build #789
Date: Tue, 22 Nov 2011 20:15:59 +0100 [thread overview]
Message-ID: <4ECBF4EF.7070705@tmatesoft.com> (raw)
Hello All,
Let me introduce our new project: SubGit (http://subgit.com/).
SubGit is a tool for smooth migration from Subversion to Git. As well as
from Git to Subversion. Without git-svn insanity.
It works like this:
- Install SubGit into your repository on the server side
- Let initial translation complete (time depends on the size of repository)
- SubGit installs hooks into repository, so it translates every svn
revision and git commit
- Committers may now use either Git or Subversion (or both) with the
tools of their choice
SubGit uses JGit to work with the Git stuff. JGit handles heavy load
perfectly thus fitting our needs, and we appreciate efforts JGit
community put into this excellent library. Thank you, guys!
SubGit EAP builds are free to use, you may try these and let us know
what do you miss, so that we make sure that all the features you need
are included into the final version of SubGit.
SubGit works on Linux, Windows or OS X and requires Java 5 or newer.
Download new SubGit EAP build from http://subgit.com/ and follow us at
@subgit and +subgit.
--
Semen Vadishev,
TMate Software,
http://subgit.com/ - Two Way Ticket to The Dark Side
next reply other threads:[~2011-11-22 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 19:15 Semen Vadishev [this message]
2011-11-23 9:03 ` [ANN] SubGit Early Access Program Build #789 Andreas Ericsson
2011-11-23 17:19 ` Semen Vadishev
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=4ECBF4EF.7070705@tmatesoft.com \
--to=semen.vadishev@tmatesoft.com \
--cc=egit-dev@eclipse.org \
--cc=git@vger.kernel.org \
--cc=jgit-dev@eclipse.org \
/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).