On 23/11/15 08:30, Pavel Raiskup wrote: > Hello maintainers, > > I planned to reuse some of my local gnulib modules in multiple projects. > > Because the modules are not yet ready to be proposed against gnulib > master, I need to keep track them "downstream". Its painful however to > C&P the local module contents all the time from project_A to project_B. > > The attached patch would help a lot: > > $ cd project_A > $ git submodule add project_B /path/to_project_B > $ gnulib --local-dir project_B/gl --local-dir gl ... > > Thanks for considering,
While a nicely written and documented change, it's quite invasive. I have the niggling feeling that if multiple projects need something, then it should just be pushed upstream? What are the conditions that would warrant this? Licensing? cheers, Pádraig.
