I like the idea of separating out the .po files if for no other reason than it expediting "grep -r". Reducing the overall repo footprint is also helpful. It doesn't matter much for a single instance, but it does add up when you have dozens of them.
Clay On Wed, Nov 10, 2010 at 8:11 AM, LAURENT Henri-Damien < [email protected]> wrote: > Hi > I propose to get etc and translator as external git repositories. > Why ? > > It would allow to have po files in their own repository and limit the > weight of Koha git archives. > For etc, it would allow to change the installer in order to keep track > of local changes for every person and therefore be able to synchronize > with community version properly. > > HOW ? > operation is simple : > git filter-branch --subdirectory-filter misc/translator -- --all > and then git push on an external repository. > for instance etc.git and translator.git on git.koha-community > This would allow to have more than one branch for etc and for instance > create and etc/apache etc/nginx etc/plack and so on... > > WHEN ? > when you think operation should be done, if you think it could be > interesting. > > and then we could have git submodules in the koha.git repository in > order to keep in synch and synchronise versions when we want. > http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html > > It is just a proposition. > -- > Henri-Damien LAURENT > _______________________________________________ > Koha-devel mailing list > [email protected] > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ >
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
