From: Marat Radchenko <marat@slonopotamus.org>
To: git@vger.kernel.org
Cc: marat@slonopotamus.org, bozaro@yandex.ru
Subject: [ANNOUNCE] git-as-svn: subversion frontend server for git repository
Date: Tue, 9 Sep 2014 15:19:04 +0400 [thread overview]
Message-ID: <20140909111903.GA13137@seldon> (raw)
Some time ago I complained [1] about troubles using Git
on a project with high ratio of non-programmers.
Since then, a conclusion was made: Git is too complex.
While Git provides many nice advanced stuff, its simplest
workflow isn't simple enough.
So we examined other options:
* Splitting project in two repos (Git + SVN). It was
thought to be the worst idea because we lost commit
atomicity
* Use GitHub SVN integration [2]. Rejected due to security
considerations: our closed-source project isn't allowed to be
hosted outside.
* Use GitHub Enterprise: rejected due to pricing
* Use SubGit [3]: rejected because of its architecture.
Then, a lost'n'forgotten git_svn_server [4] was found. After playing
with it, we found out that its approach can work, though several
decisions (Python and extensive forking of `git`) made it very slow.
So we thought "we're programmers, after all".
And that's when *git-as-svn* [5] was born. It is a daemon that sits
on top of Git repository and talks svn:// protocol.
Features supported:
* checkout/update
* log
* blame
* commit (!)
* rename detection (though a bit slow yet)
* svn:eol-style
* Git pre-receive hooks
* simple or LDAP authentication
* partial checkout
* sparse working copy (svn --depth/--set-depth)
* git submodules
Current limitations:
* Only a single Git branch from a single repository
* Needs at least one commit in Git
* Parses whole history on startup and doesn't cache it anywhere
* You must not do 'inverted merges'. Old HEAD must be reachable from
new HEAD by first-parent traversal.
[1]: http://marc.info/?l=git&m=139866660018802
[2]: https://help.github.com/articles/support-for-subversion-clients
[3]: http://subgit.com/
[4]: http://git.q42.co.uk/git_svn_server.git
[5]: https://github.com/bozaro/git-as-svn/
next reply other threads:[~2014-09-09 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 11:19 Marat Radchenko [this message]
2014-09-09 16:49 ` [ANNOUNCE] git-as-svn: subversion frontend server for git repository Junio C Hamano
2014-09-09 18:57 ` Marat Radchenko
2014-09-09 19:30 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140909111903.GA13137@seldon \
--to=marat@slonopotamus.org \
--cc=bozaro@yandex.ru \
--cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).