Le 16/01/16 12:48, Guenter Milde a écrit :
Or we remove this generated file from git (my preference).
This creates problems of its own, since now there are files in
/lib.
JMarc
Le 16/01/2016 10:12, Georg Baum a écrit :
Guillaume Munch wrote:
I believe as well that we should not extend the already long checklist
for format changes. Updatedocs could take care of running gen_lfuns and
then update it to the latest format.
Good idea. I added the generation of LFUNs.lyx,
Guillaume Munch wrote:
> I believe as well that we should not extend the already long checklist
> for format changes. Updatedocs could take care of running gen_lfuns and
> then update it to the latest format.
Good idea. I added the generation of LFUNs.lyx, the version updating did
exist
On 2016-01-16, Georg Baum wrote:
> Guillaume Munch wrote:
>> I believe as well that we should not extend the already long checklist
>> for format changes. Updatedocs could take care of running gen_lfuns and
>> then update it to the latest format.
> Good idea. I added the generation of LFUNs.lyx,
Le 15/01/2016 20:32, Georg Baum a écrit :
commit 4c3b8bf7c7205e26b28b6562be11105558ec3250
Author: Georg Baum
Date: Fri Jan 15 21:31:57 2016 +0100
Update LFUNs.lyx to current format
diff --git a/development/tools/gen_lfuns.py b/development/tools/gen_lfuns.py
index
Guillaume Munch wrote:
> Is a step in Development.lyx missing?
IIRC we did not decide that yet. IMHO it is not required to update these
files for each format change, but some time ago we decided that for a
release all files should be up to date, and it is in the release checklist.
Georg
Le 15/01/2016 20:50, Georg Baum a écrit :
Guillaume Munch wrote:
Is a step in Development.lyx missing?
IIRC we did not decide that yet. IMHO it is not required to update these
files for each format change, but some time ago we decided that for a
release all files should be up to date, and it