Yes, git-svn lacks quite a few features and can be problematic. Besides, 1 VCS and 1 way of doing things (ie. Git only everywhere) is always easier to manage than SVN here, a read-only delayed (possibly by months, when it breaks) Git copy on GitHub, and possibly git-svn on the users' end.
On Mon, Sep 18, 2017 at 9:25 AM, Peter kovacs <pe...@apache.org> wrote: > I failed using git svn clone ... > Git is doing some history scans that cause to run for forever. I have not > found any way to circumvent that scan. > > I have forked the apache repo on github and then pulled from there. That's > an easier workflow for me. > What I miss is a push functionallity. But that's for me only convenience. > I can work with git and svn. No issue for me. > > So I am quite neutral on the topic. > > All the best > Peter > > Am 17. September 2017 20:12:13 MESZ schrieb Andrea Pescetti < > pesce...@apache.org>: > >Patricia Shanahan wrote: > >> The big new developer issue may be lack of Subversion experience. Git > >> seems to be the repository-of-the-decade. > > > >This can be circumvented by using git as follows: > > > >$ git svn clone > >https://svn.apache.org/repos/asf/openoffice/branches/AOO414 > > > >and similar. I would honestly use one of the two mirrors I mentioned > >earlier, but we could include a section describing these methods to get > > > >the code without using a dedicated Subversion client. > > > >Regards, > > Andrea. > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > >For additional commands, e-mail: dev-h...@openoffice.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
