lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Policy decision needed about Documentation/snippets/new


From: John Mandereau
Subject: Re: Policy decision needed about Documentation/snippets/new
Date: Wed, 18 Jul 2012 16:26:30 +0200

Il giorno mer, 18/07/2012 alle 14.32 +0100, Phil Holmes ha scritto:
> From: "Graham Percival" <address@hidden>
> Sent: Wednesday, July 18, 2012 2:18 PM
> > On Wed, Jul 18, 2012 at 03:08:55PM +0200, John Mandereau wrote:
> >> Note that in the case you change a single or a couple of snippets in
> >> Documentation/snippets/new and don't want to update everything by
> >> downloading and unpacking a tarball from LSR website, there are
> >> currently contradictory instructions:
> >> * one page tells to run makelsr.py
> >> http://lilypond.org/doc/v2.15/Documentation/contributor/adding-and-editing-snippets
> >
> > This is the correct option.
> 
> Agreed.

OK, so makelsr.py may need to be fixed.


> I certainly think this is the best option until we've let the new system get 
> shaken down - i.e. minimum other changes.

All right.


> >> 2) Other behaviour
> 
> I think this is really "A suggested alternative" ?

Yes, it is.


> I think the idea of building snippet documentation so that snippets in new 
> take priority in the build from snippets in snippets is a good suggestion. 
> I do think it would be better to hold off for a bit - as I said, let the new 
> system shake down a bit.

OK, in this case I'm going to submit for review a patch to makelsr and
the CG for option 1)

Cheers,
John




reply via email to

[Prev in Thread] Current Thread [Next in Thread]