Karl Berry writes:
> sync them manually
>
> FWIW, this is precisely what gnulib/config/srclist* is about: keeping
> individual files in sync between different places, unrelated to any
> "module" concept. It is not gnulib-specific (or git-specific or
> anything-specific). -k
I didn't know
Mike Frysinger writes:
> On 14 Jan 2016 00:59, Mathieu Lirzin wrote:
>> However in the case of GNU packages which don't use C, It is a bit
>> overkill to clone a full repository only for some maintenance scripts
>> and a robust bootstrap script which fetches .po files.
>> []
>> What do people
sync them manually
FWIW, this is precisely what gnulib/config/srclist* is about: keeping
individual files in sync between different places, unrelated to any
"module" concept. It is not gnulib-specific (or git-specific or
anything-specific). -k
On 14 Jan 2016 00:59, Mathieu Lirzin wrote:
> For C projects, it is really convenient to use Gnulib as a Git submodule
> and let ‘./bootstrap’ do the job. However in the case of GNU packages
> which don't use C, It is a bit overkill to clone a full repository only
> for some maintenance scripts an
Hi,
For C projects, it is really convenient to use Gnulib as a Git submodule
and let ‘./bootstrap’ do the job. However in the case of GNU packages
which don't use C, It is a bit overkill to clone a full repository only
for some maintenance scripts and a robust bootstrap script which fetches
.po f
