Oh, I think I was a bit unclear. I wasn't suggesting expanding the "migration". Rather just using this approach for apertium-fin so that previous SVN check outs would not break and that any other links would work.
Regarding point 2, git submodules make it fairly painless to achieve such a structure. -- Sushain Cherivirala www.skc.name On Jul 28, 2015 2:09 PM, "Francis Tyers" <[email protected]> wrote: > A 2015-07-28 23:51, Sushain Cherivirala escrigué: > > Fran, > > > > It could be made so that each Github repo, e.g. > > mygithubuser/apertium-fin, would map to a subdirectory in the SVN > > repo, e.g. /languages/apertium-fin. An arbitrary number of such > > mappings could be maintained. > > > > Would this approach conflict with current standards? > > Yes, > > 1) If things are on github it wouldn't make sense to keep anything in > SVN, especially not readonly. > > 2) It would require a minimum of 182 subrepositories in github, and I'm > not sure how we would have subsub modules in a way that each can be > checked out individually (e.g. > apertiumgithubuser/languages/apertium-kaz) etc. > > F. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Apertium-stuff mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/apertium-stuff >
------------------------------------------------------------------------------
_______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
