>> My question: Is this really a problem? Are such fixes lost if >> someone is running makelsr? > > Depends, and yes.
Hmm, hmm, hmm. > Files are completely rewritten from a makelsr import. Whether or > not this is a problem depends on the changes that you've been > making. Well, I consider it a `problem' if fixes get completely overwritten by non-fixed files... >> Or is someone taking care of such fixes, probably transferring them >> to the LSR? > > Certainly nobody is doing that. OK. > Of course, these days nobody is doing lsr imports either. But makelsr gets called quite frequently (e.g. Jul 29th, Jul 20th, and you did it on Jul 16th)... Oh, wait. It seems that `makelsr' is a misnomer. The script actually takes care only of directories full of lilypond snippets, but it is not directly related to the LSR on the Italian host, right? You essentially use it to transfer snippets from your local (translation or whatever) git branch into the trunk. >> It's really tedious to add fixed files to the `new' directory... > > This might be made easier with a script, or at least if we cleared > out the old stuff from that "new" directory. > > Unfortunately, nobody is willing to demonstrate that they care > about LSR, so we're floating in limbo. And I've just remembered that the `snippets/new' directory refers to `new features' in lilypond, not to `new files'. My conclusion is that it is quite safe to directly edit files in the `snippets' directory. Relieved :-) Werner _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel