# [ANN] SubGit Early Access Program Build #789

3 messages from 2011-11-22 to 2011-11-23. Participants: Semen Vadishev, Andreas Ericsson.
Thread: https://gitlist.dev/t/29000

## Semen Vadishev, 2011-11-22 19:15

Subject: [ANN] SubGit Early Access Program Build #789
Message-ID: <4ECBF4EF.7070705@tmatesoft.com>
URL: https://gitlist.dev/e/4ECBF4EF.7070705%40tmatesoft.com

```
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

```

## Andreas Ericsson, 2011-11-23 09:03

Subject: Re: [ANN] SubGit Early Access Program Build #789
Message-ID: <4ECCB6C6.8040200@op5.se>
URL: https://gitlist.dev/e/4ECCB6C6.8040200%40op5.se
In-Reply-To: <4ECBF4EF.7070705@tmatesoft.com>

```
On 11/22/2011 08:15 PM, Semen Vadishev wrote:
> 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
> 

How does it handle merges?

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

```

## Semen Vadishev, 2011-11-23 17:19

Subject: Re: [ANN] SubGit Early Access Program Build #789
Message-ID: <4ECD2B24.5050802@tmatesoft.com>
URL: https://gitlist.dev/e/4ECD2B24.5050802%40tmatesoft.com
In-Reply-To: <4ECCB6C6.8040200@op5.se>

```
Hello Andreas,


> How does it handle merges?
The short answer is

1. git to svn: SubGit sets svn:mergeinfo accordingly to
the history of merged parent(s).

2. git to svn: SubGit checks whether modified svn:mergeinfo includes 
the history of a certain branch, if so it adds this branch as a merge 
parent.

For more details please refer to
http://subgit.com/documentation/spec/merge.pdf — it's a part of SubGit
specification related to the merge-tracking stuff.


Semen Vadishev,
TMate Software,
http://subgit.com/ - Two Way Ticket to The Dark Side


On 23 November 2011 10:03, Andreas Ericsson wrote:
> On 11/22/2011 08:15 PM, Semen Vadishev wrote:
>> 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
>>
> How does it handle merges?
>

```