On Tue, Sep 28, 2010 at 06:30:12PM -0700, Mark Polesky wrote:
> Graham Percival wrote:
> > Technically, the doc policy (or at least custom) is to
> > have a blank newline before the @end itemize / @end
> > enumerate, but I don't know if that has any effect on
> > anything. I just always do it that
Graham Percival wrote:
> Technically, the doc policy (or at least custom) is to
> have a blank newline before the @end itemize / @end
> enumerate, but I don't know if that has any effect on
> anything. I just always do it that way because previous
> material did it that way, and I was never curiou
LGTM, go ahead an push.
Technically, the doc policy (or at least custom) is to have a blank
newline before the @end itemize / @end enumerate, but I don't know if
that has any effect on anything. I just always do it that way because
previous material did it that way, and I was never curious enoug
On 2010/09/26 17:24:07, Graham Percival wrote:
Documentation/notation/pitches.itely:142:
Why the extra newline ?
Fixed.
Documentation/notation/repeats.itely:682:
Why is this @samp instead of @code?
Rewritten. Should be fine, but feel free to
double-check it.
- Mark
http://codereview.apps
LGTM, although I didn't check that it still compiles.
http://codereview.appspot.com/2217046/diff/1/Documentation/notation/pitches.itely
File Documentation/notation/pitches.itely (right):
http://codereview.appspot.com/2217046/diff/1/Documentation/notation/pitches.itely#newcode142
Documentation/n
Reviewers: ,
Message:
Anyone want to double-check this doc patch?
Just trying to clean up the NR a little bit
in light of recent discussions on -devel.
Thanks
- Mark
Description:
Doc: NR 1: Use @co...@var{...}} for variables.
Please review this at http://codereview.appspot.com/2217046/
Affec
