Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(2174)

Issue 5492066: Doc: Canged @table example in Usage (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
12 years, 4 months ago by pkx166h
Modified:
12 years, 4 months ago
Reviewers:
Ian Hulin (gmail)
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Doc: Canged @table example in Usage In response to Tracker Item 2114 Application Usage 1.2 Changed the way the @table is formatted so that the single quotes are removed. Took some time to edit he linebreaks within the *.itely file so that it follows the line lengths as per the CG. Minor line spacing edits to make existing @cindex and @item enries clearer to see in the source file for future editing

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+51 lines, -45 lines) Patch
M Documentation/usage/running.itely View 7 chunks +51 lines, -45 lines 1 comment Download

Messages

Total messages: 3
pkx166h
I'm deprecating this because of another Tracker Item that I can also add in a ...
12 years, 4 months ago (2011-12-17 13:11:26 UTC) #1
Ian Hulin (gmail)
Hope this isn't too late. Please apply the change to your new patch. Cheers, Ian ...
12 years, 4 months ago (2011-12-17 15:45:20 UTC) #2
pkx166h
12 years, 4 months ago (2011-12-17 19:50:03 UTC) #3
Ian,

On 17 December 2011 15:45,  <ianhulin44@gmail.com> wrote:
> Hope this isn't too late.  Please apply the change to your new patch.
>
> Cheers,
> Ian
>
>
> http://codereview.appspot.com/5492066/diff/1/Documentation/usage/running.itely
> File Documentation/usage/running.itely (right):
>
>
http://codereview.appspot.com/5492066/diff/1/Documentation/usage/running.itel...
> Documentation/usage/running.itely:241: The safe mode will prevent many
> useful LilyPond snippets from being
> "Safe mode will prevent many useful LilyPond snippets from being"
>
> http://codereview.appspot.com/5492066/

It was too late :)

Sorry for that (and to anyone else who looked at the first patch), I
started on one Tracker then made the patch/upload but then while doing
another tracker issue I saw it was different request in the same
'area' of doc so decided to make a single patch for two issues to save
having to review two Rietvelds for relatively small changes. At least
that was the theory.

However I'll add this edit request to the 'other' issue and make a new patch

Thanks for reviewing.

-- 
--

James
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b