Thanks for the pointers. This would solve one part of the problem - having to commit in separate repositories and branching each one when working on features that cut across projects.
However, it doesn't solve the overhead of making releases of 6 different packages and clicking the buttons in Launchpad, making tarballs, release notes etc for each one. -- Anders On Sat, Feb 09, 2013 at 03:02:45PM +0100, Roland Siegbert wrote: > Myles, > thank you for this one. :-) >> Just a note to say that if FEniCS is going to move to git (yes please) >> and consider 'git submodule' then you would benefit from looking at 'git >> subtree'. I am just going to quote the man page: > It's even already included into git since git-1.7.11, though it seems > to be quite young! Workstation here: LM14 w/ git-1.7.10.4 - however, > there is a origin/hack: https://github.com/apenwarr/git-subtree. > I really like that this approach, as it seems to be free of any > overhead and it is even possible to "export" the commits done in the > monolithic repo to the subtree repo. > Roland > Further reading for anybody interested: > [1]: http://log.pardus.de/2012/08/modular-git-with-git-subtree.html > It seems they had a similar problem at the Horde Project. > _______________________________________________ > Mailing list: https://launchpad.net/~fenics > Post to : [email protected] > Unsubscribe : https://launchpad.net/~fenics > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~fenics Post to : [email protected] Unsubscribe : https://launchpad.net/~fenics More help : https://help.launchpad.net/ListHelp
