Re: LSR, updates and committishes

[John Mandereau]

Francisco Vila a écrit :
> 2009/5/25, John Mandereau <address@hidden>:
>   
> >  You should run makelsr.py *before* you commit changes to texidocs, not
> > after. Try it as explained in the CG, and you'll see (how) it works.
> >     
>
> Hello, I'm in trouble. I have run makelsr.py and git status gives
>
>   
Before looking at your (rather scary in this case) "git status" output, 
have you examined output of makelsr.py?
Have you realized makelsr.py requires fresh snapshots compiled from Git 
of lilypond and convert-ly, as
explained in the CG? You can set them in PATH without installing them by 
using something described in
HACKING; btw I should explain this in the CG, this would stop me 
compiling and installing binary snapshots
regularly.

> # On branch lilypond/translation
> # Changed but not updated:
> #   (use "git add/rm <file>..." to update what will be committed)
> #
> #       deleted:    input/lsr/accordion-discant-symbols.ly
> #       deleted:    input/lsr/adding-a-figured-bass-above-or-below-the-notes.ly
> #       deleted:    input/lsr/adding-ambitus-per-voice.ly
> #       deleted:    input/lsr/adding-an-extra-staff-at-a-line-break.ly
> #       deleted:    input/lsr/adding-an-extra-staff.ly
>   
Did you pass makeslr.py an argument? You shouldn't have, unless you know 
why.


> As LSR is being updated these days, maybe
> you'll suggest not to make texidoc work on my side, right?
>   

Certainly not, I hope we manage to make things clear.

John