Updates:
Owner: ---
Comment #17 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
A lot of these things were never added to the 2.12 docs (or 2.10, or
2.8...). But with the old doc system, th
Comment #16 on issue 989 by hanwenn: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
graham,
not wanting to rain on anyone's parade, but why are you holding back the
release for this? Have these things been removed from the 2.12
Comment #15 on issue 989 by pkx1...@hotmail.com: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Just an update as I have been doing most of the work here.
According to:
http://wiki.lilynet.net/index.php/Regtests
I have left to do/v
Comment #14 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
PS the easiest way to figure out what's "blocking work" would just be to go
to the top of the list and find the first regtest that isn't c
Comment #13 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
The biggest problem right now is the lack of somebody organizing this
effort. See
http://lists.gnu.org/archive/html/lilypond-devel/2010-
Comment #12 on issue 989 by kie...@alumni.rice.edu: ensure that no
information is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Can I help with this issue?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lis
Comment #11 on issue 989 by kie...@alumni.rice.edu: ensure that no
information is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Can I do this one?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.or
Comment #10 on issue 989 by percival.music.ca: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
postfix \cresc should be documented elsewhere than the regtests.
___
bug-lilypond mailing lis
Updates:
Status: Started
Comment #9 on issue 989 by pnorcks: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
(No comment was entered for this change.)
___
bug-lilypond mailing list
Comment #8 on issue 989 by percival.music.ca: ensure that no information is
only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Comment 7: committed.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred th
Comment #7 on issue 989 by pkx1...@hotmail.com: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Graham, here is a patch to show the non-integer example for \bendAfter in
the NR i
haven't touched any snippets though - they still show
Comment #6 on issue 989 by v.villenave: ensure that no information is only
in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Thanks for posting this howto, Graham. I've been ill for a few days and
it's not
getting any better, but I'll go on with the regtest-review as so
Comment #5 on issue 989 by percival.music.ca: ensure that no information is
only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Unfortunately, most of the regtests that Valentin picked out don't have
anything to
do with the NR, so it's not your concern. The first on
Comment #4 on issue 989 by pkx1...@hotmail.com: ensure that no information
is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I can help with the NR stuff. I have looked at the Wiki but don't really
understand
what it is that needs documenting. Sorry to be slow.
Comment #3 on issue 989 by v.villenave: ensure that no information is only
in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I have begun an extensive review of the regtests, my current progression
may be seen
on http://wiki.lilynet.net/index.php/Regtests
We need some
Comment #2 on issue 989 by percival.music.ca: ensure that no information is
only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Great! A few more tidbits:
- you don't need to write the docs yourself; just keep track of regtest
filenames
with info we should add.
-
Updates:
Owner: v.villenave
Comment #1 on issue 989 by v.villenave: ensure that no information is only
in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
I'm taking ownership of this one. Not that I won't welcome any help in
handling it;
any (preferably experienc
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Critical
New issue 989 by percival.music.ca: ensure that no information is only in
the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Some information can only be found in regtests... even worse, it's only
prese
18 matches
Mail list logo
