On Sun, Feb 10, 2013 at 10:16:25AM +0100, jeremy rosen wrote: > 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
How would it interact with developers who want to use translations? Also how will it affect releasing, both tagging and making tarballs. > (that last point is not true for music/art unfortunately) > > we also mentionned the resource branch that could be a separate repo... Yes I also mentioned that in my mail. > btw, mordante do you know if the limit is per repo or if it would be > for the wesnoth user ? >From reading the GitHub website it looks like per repo. Note when we want to split the repo to reduce its size it also means we have to historically remove those commits. It seems to be possible with git filter-branch as said by GitHub, but I'm what reluctant to start to modify the history. -- Regards, Mark de Wever aka Mordante/SkeletonCrew _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
