Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-03-02 Thread janek . lilypond
pushed as 90ee61d5b681295b8b401128ca9bc48554eee66a closed http://codereview.appspot.com/5669047/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-26 Thread janek . lilypond
Screw this; i tried using regular refs but they produced hideous effects in html. I'm going back to named references; they are not perfect but acceptable i'd say. http://codereview.appspot.com/5669047/ ___ lilypond-devel mailing list

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-25 Thread janek . lilypond
New patch set uploaded, it should make doc now. Thanks for the tips, Carl and Graham! You saved me some time. I decided not to use @rglos and @rinternals (because from what i understand it would print the name of the section i'm referring to) but use @rglosnamed and @rinternalsnamed instead.

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-25 Thread Graham Percival
On Sat, Feb 25, 2012 at 09:51:31PM +, janek.lilyp...@gmail.com wrote: I decided not to use @rglos and @rinternals (because from what i understand it would print the name of the section i'm referring to) but use @rglosnamed and @rinternalsnamed instead. I discourage (but not forbid) the use

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-25 Thread Janek Warchoł
On Sat, Feb 25, 2012 at 10:55 PM, Graham Percival gra...@percival-music.ca wrote: Up to you.  The fancier you make the formatting, the harder it is to maintain.  You should also check how it looks in info.  If you want to play games with that, go ahead -- as I said, we don't forbid @...named.  

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-23 Thread Graham Percival
On Wed, Feb 22, 2012 at 11:24:22PM +, janek.lilyp...@gmail.com wrote: Could you help me with links to music glossary and internals? Julien wrote that they are wrong, and i don't know how they should be done (and i'm really busy so if you can save me 15 minutes of searching i'd be

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-23 Thread Carl Sorensen
On 2/23/12 3:13 PM, Graham Percival gra...@percival-music.ca wrote: On Wed, Feb 22, 2012 at 11:24:22PM +, janek.lilyp...@gmail.com wrote: Could you help me with links to music glossary and internals? Julien wrote that they are wrong, and i don't know how they should be done (and i'm

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-22 Thread janek . lilypond
New patch set uploaded. On 2012/02/17 12:04:10, Graham Percival wrote: http://codereview.appspot.com/5669047/diff/5001/Documentation/contributor/regressions.itexi File Documentation/contributor/regressions.itexi (right):

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-17 Thread graham
http://codereview.appspot.com/5669047/diff/5001/Documentation/contributor/regressions.itexi File Documentation/contributor/regressions.itexi (right): http://codereview.appspot.com/5669047/diff/5001/Documentation/contributor/regressions.itexi#newcode512

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-14 Thread graham
http://codereview.appspot.com/5669047/diff/1/Documentation/contributor/regressions.itexi File Documentation/contributor/regressions.itexi (right): http://codereview.appspot.com/5669047/diff/1/Documentation/contributor/regressions.itexi#newcode511 Documentation/contributor/regressions.itexi:511:

Re: CG: add information about Regtest Checking Project (issue 5669047)

2012-02-14 Thread janek . lilypond
http://codereview.appspot.com/5669047/diff/1/Documentation/contributor/regressions.itexi File Documentation/contributor/regressions.itexi (right): http://codereview.appspot.com/5669047/diff/1/Documentation/contributor/regressions.itexi#newcode511 Documentation/contributor/regressions.itexi:511: