On Wed, Sep 19, 2012 at 3:34 PM, Alexander Kitaev <kitaev_at_tmatesoft.com> wrote:
> Hello All,
>
> Our team is proud and delighted to announce SubGit 1.0.0 release!
> New version is available for download at SubGit web site at http://subgit.com/
>
> SubGit is a server-side tool for a smooth, stress-free Svn to Git
> migration. SubGit lets one to set up a bidirectional Subversion to Git
> replication (writable mirror) and thus it allows users to choose
> freely between Subversion and Git version control systems.
Except, of course when it doesn't. The use of OS specific EOL, which
git does not support, and subversion keywords like $Id$ and $Author$,
which git does not support, would seem to me to be an adventure
begging to happen.
> SubGit is a closed source Java application, which is free for use in
> Open Source and Academic projects, as well as in any repository with
> up to 10 committers. Besides, there are no limitations on the time you
> may evaluate SubGit in commercial or closed source projects.
And I'm afraid to say this sounds like a really, really bad idea on
the server side. There are enough inconsistencies in merging
technologies of each system and in the workflow that it *sounds* like
those gods-awful screws that have both flathead slots and Phillips
head crossed slots in them:
> A few useful links:
>
> SubGit Web Site: http://subgit.com/
> SubGit Book: http://subgit.com/book/ - nice illustrated guide that
> would help you to install, configure and use SubGit
> SubGit Issues Tracker: http://issues.tmatesoft.com/issues/SGT
>
> With best regards,
> Alexander Kitaev,
> TMate Software,
> http://subgit.com/ - Safe Svn to Git Migration!
> http://svnkit.com/ - Java [Sub]Versioning Library!
> http://hg4j.com/ - Java Mercurial Library!
> http://sqljet.com/ - Java SQLite Library!
Java has its uses. Replacing a full-blown, fully implemented C++
codebase where the maintainers, who also set the API's, are all
working in C++ means entirely different models of file handling,
memory management, and maintaining compatibility with a dynamic and
evolving codebase, in another language..... sounds like the very, umm,
"clever" engineer I knew who tried to write a source control system
based on checked out branches having locked files owned by root and
hardlinked to the original code. It sounded like an efficient idea on
paper, but lord, it was painful to clean up after.
Received on 2012-09-20 06:14:24 CEST