Re: [ANNOUNCE] git-as-svn: subversion frontend server for git repository

2014-09-09 Thread Junio C Hamano
Marat Radchenko writes: >> > * You must not do 'inverted merges'. Old HEAD must be reachable from >> > new HEAD by first-parent traversal. >> >> I am not sure what you mean by this to properly assess how >> significant this limitation is. Care to draw a simple picture? > > SVN doesn't sup

Re: [ANNOUNCE] git-as-svn: subversion frontend server for git repository

2014-09-09 Thread Marat Radchenko
On Tue, Sep 09, 2014 at 09:49:03AM -0700, Junio C Hamano wrote: > Marat Radchenko writes: > > > Some time ago I complained [1] about troubles using Git > > on a project with high ratio of non-programmers. > > ... > > Then, a lost'n'forgotten git_svn_server [4] was found. > > ... > > Interesting.

Re: [ANNOUNCE] git-as-svn: subversion frontend server for git repository

2014-09-09 Thread Junio C Hamano
Marat Radchenko writes: > Some time ago I complained [1] about troubles using Git > on a project with high ratio of non-programmers. > ... > Then, a lost'n'forgotten git_svn_server [4] was found. > ... Interesting. > Current limitations: > ... > * You must not do 'inverted merges'. Old HEAD m

[ANNOUNCE] git-as-svn: subversion frontend server for git repository

2014-09-09 Thread Marat Radchenko
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 proj