Re: branching stable/2.22?

[David Kastrup]

Han-Wen Nienhuys <hanwenn@gmail.com> writes:

> On Sat, Sep 12, 2020 at 11:28 AM Jonas Hahnfeld <hahnjo@hahnjo.de> wrote:
>>
>> > >> Similarly, if I change a documentation string in an SCM file like
>> > >> `define-markup-commands.scm`, the documentation doesn't get
>> > >> rebuilt, either.
>> > >
>> > > I can look at reintroducing the SCM -> texi dependencies.
>> >
>> > Please do so.  Due to the auto-generation process, it is far from
>> > trivial to find out which command has to be called.
>>
>> Actually, I value faster incremental builds that sometimes does less
>> over wasting my time always regenerating the internals manual whenever
>> I happen to touch an SCM file. Just doing
>>  $ rm Documentation/out*/en/internals.texi
>> will update it, no need to remember any command.
>
> I see the value of faster builds, but I think being correct is more
> important than being fast.
>
> What annoys me is that the default build creates the info docs, which
> aren't necessary for developing lilypond.

This checks, for example, music function comments for correct Texinfo
syntax (even if it does not test embedded LilyPond for validity).

-- 
David Kastrup