On Wed, Jul 29, 2015 at 9:37 AM, Aboobacker MK <[email protected]> wrote:
> I meant "also an svn repository" see these articles > https://help.github.com/articles/support-for-subversion-clients/ , > https://github.com/blog/1178-collaborating-on-github-with-subversion > I did not know of this. While this is a useful feature for Apertium commiters not comfortable learning git, it's still just their subversion bridge, not directly an SVN repository. There are some possible problems: 1) If it follows the standard SVN trunk/branch structure which Apertium's SVN repo does not conform to, the repository structure would need to be refactored a little bit. 2) AFAIK git svn has some issues with commit checksums <https://git-scm.com/book/en/v1/Git-and-Other-Systems-Git-and-Subversion#Committing-Back-to-Subversion>. This is a different case (svn-to-github), so maybe the issue is not present here. However, if there are no issues in using both the svn and git client in parallel on a github repo, this would really make the transition much less painful for commiters. On 29 Jul 2015 04:34, "Sushain Cherivirala" <[email protected]> wrote: > > Regarding point 2, git submodules make it fairly painless to achieve such > a structure. > +1 Hrvoje
------------------------------------------------------------------------------
_______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
