Bruno Haible writes:
> Hi José,
>
>> In GNU poke we use the gendocs gnulib module. We also customize our
>> doc/gendocs_template, which is committed in our VCS.
>>
>> This leads to the situation where each time we run `bootstrap', it
>> copies the unmodified gendocs_template over to our tree, o
Hi Bruno.
I just pushed a fix in poke implementing the A) approach below.
Thanks!
> Hi José,
>
>> In GNU poke we use the gendocs gnulib module. We also customize our
>> doc/gendocs_template, which is committed in our VCS.
>>
>> This leads to the situation where each time we run `bootstrap', i
Hi José,
> In GNU poke we use the gendocs gnulib module. We also customize our
> doc/gendocs_template, which is committed in our VCS.
>
> This leads to the situation where each time we run `bootstrap', it
> copies the unmodified gendocs_template over to our tree, overwritting
> the customized ve
Hello people!
In GNU poke we use the gendocs gnulib module. We also customize our
doc/gendocs_template, which is committed in our VCS.
This leads to the situation where each time we run `bootstrap', it
copies the unmodified gendocs_template over to our tree, overwritting
the customized version
