Re: output-distance.py

[Jean-Charles Malahieude]

Le 01/10/2009 20:45, Patrick McCarty disait :
> On 2009-10-01, Jean-Charles Malahieude wrote:
> > In fact, it was on a fresh local clone of the master branch as of
> > Reinhold's "Fix killCues ..." patch dated 2009-09-30 15:44:45. I
> > never did a 'test-baseline' before.
> > Would you like me to clean everything, rewind to 4c5a581ca, make a
> > test-baseline (and save the logs), and then rebuild as of a clean
> > current master?  I'm available for the next 5 hours, going forward
> > on my translation process (in a separate directory/clone)...
>
> Sure, I think that would be helpful.
>
> Thanks,
> Patrick

OK. Here is what I've done :

1.1- open a gitk window to obtain what was the commit message to the 
commit preceding 4c5a581ca (lilypond-book: Change md5 hashing strategy). 
 It was labeled "Docs: LM 3.3: Clarify \score and \new Score"
posted by Trevor on the 28th of September.

1.2- browse on savannah to find commit
"Docs: LM 3.3: Clarify \score and \new Score"

1.3- click on the "snapshot" link to download a gzipped repository of 
Lily-master to that point.

1.4- uncompress that archive, run "autogen.sh" and "make test-baseline" 
in the new created directory. Nothing is hurting me...

2.1- clone a freshly updated master repository (as of my Doc-fr oops)

2.2- run "autogen.sh" and "make test-baseline" on it. Nothing hurts.

I've saved the logs.  Do you want anything else?
I'm now building the documentation on master, and will save the logs...

Cheers,
Jean-Charles