jeremy rosen <[email protected]>:
> having translations in a separate repo could be nice...
>
> * it would allow to give direct git commit right to some translators
> * wesnoth runs fine without translations so it shouldn't bother normal devs
> much
I think that first point is a very strong one. More generally, we want to make
separate repositories for any branch or subtree that naturally has a different
privilege group.
> (that last point is not true for music/art unfortunately)
Yes, but we could handle all of translations, music and art with
externals - kept in separate repositories that are automatically
pulled into subdirectories when you pull the master.
> we also mentioned the resource branch that could be a separate repo...
Yes, I think it should be.
One of the advantages of my reposurgeon tool is that it will make carving the
existing repository into pieces by path or branch an easy thing to do. That
is, providing it has enough disk space for the whole SVN repo. I think I had
better implement blob compression. :-)
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>
_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev
