----- Original Message -----
From: "Trevor Daniels" <t.dani...@treda.co.uk>
To: "James Lowe" <james.l...@datacore.com>; <tdanielsmu...@googlemail.com>
Cc: "Lily-Devel List" <lilypond-devel@gnu.org>
Sent: Thursday, August 04, 2011 2:46 PM
Subject: Re: Doc: Added \compoundMeter function to NR (issue4837050)
James, you wrote Thursday, August 04, 2011 11:55 AM
)[mailto:lilypond-devel-bounces+james.lowe=datacore....@gnu.org] On
)Behalf Of tdanielsmu...@googlemail.com
)Sent: 04 August 2011 09:32
)Also, you can't just delete the unwanted snippets from the git
tree -
)they'll reappear at the next LSR update. You'll need to delete
them from
)snippets/rhythms.snippet-list and change the entries in the LSR to
)remove them from the docs.
I wasn't sure about snippets/rhythms.snippets-list as I thought
this was autogenerated? I
deliberately didn't touch this thinking that it would be
re-autogenerated and so it would be
missing because I had removed the file.
So just to be clear do I need to edit this *-list file AND change
the entry in the LSR to 'remove' > or is just the LSR enough?
You could just delete the snippets from the LSR, and ask Phil to run
LSR update at the same time as your doc change was committed, but
doing it in sync is going to be tricky. Better to edit
snippets-list in the same commit as your doc change and snippet
deletion - that way git is kept consistent. The LSR can then be
changed anytime after that as long as it's before the next LSR
update.
Copied to devel so my advice can be corrected if it's wrong.
Trevor
I don't run LSR update: I'm an authoriser, but that's all.
--
Phil Holmes
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel