https://codereview.appspot.com/6948070/diff/3001/Documentation/contributor.texi
File Documentation/contributor.texi (right):
https://codereview.appspot.com/6948070/diff/3001/Documentation/contributor.texi#newcode70
Documentation/contributor.texi:70:
On 2012/12/25 08:05:45, Trevor Daniels wrote:
LGTM, apart from a couple of nitpicks which
I missed earlier. No need to post a new
patch-set.
https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (left):
I'm happy with this with the change below.
The formatting of this section (and the
CG in general) has never been systematically
reviewed, so there's no point in being
strict about it here. The text is understandable
even though it doesn't fit into the surrounding
material in the best possible
https://codereview.appspot.com/7013043/diff/1/Documentation/contributor/doc-work.itexi
File Documentation/contributor/doc-work.itexi (right):
https://codereview.appspot.com/7013043/diff/1/Documentation/contributor/doc-work.itexi#newcode155
Documentation/contributor/doc-work.itexi:155: The
hello,
On 26 December 2012 11:00, d...@gnu.org wrote:
https://codereview.appspot.com/7013043/diff/1/Documentation/contributor/doc-work.itexi
File Documentation/contributor/doc-work.itexi (right):
https://codereview.appspot.com/7013043/diff/3003/Documentation/contributor/doc-work.itexi
File Documentation/contributor/doc-work.itexi (right):
https://codereview.appspot.com/7013043/diff/3003/Documentation/contributor/doc-work.itexi#newcode149
Documentation/contributor/doc-work.itexi:149:
James pkx1...@gmail.com writes:
On 26 December 2012 11:00, d...@gnu.org wrote:
Documentation/contributor/doc-work.itexi:155: The correct way to add
[changes like this] to the documentation is to
Why the [] ?
This is a standard way to to clarify the antecedent.
Another frequent use is
https://codereview.appspot.com/7013043/diff/3003/Documentation/contributor/doc-work.itexi
File Documentation/contributor/doc-work.itexi (right):
https://codereview.appspot.com/7013043/diff/3003/Documentation/contributor/doc-work.itexi#newcode158
Documentation/contributor/doc-work.itexi:158:
https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (left):
https://codereview.appspot.com/6948070/diff/6001/Documentation/notation/notation-appendices.itely#oldcode1545
Hello,
On 26 December 2012 12:52, philehol...@googlemail.com wrote:
https://codereview.appspot.com/7013043/diff/3003/Documentation/contributor/doc-work.itexi
File Documentation/contributor/doc-work.itexi (right):
On 2012/12/26 13:15:05, J_lowe wrote:
Is there any case where a snippet would not have the docs tag?
James
Some statistic from the last LSR-update:
The 2.12.3-LSR contained 645 snippets.
291 were tagged docs.
There are many LSR-snippets showing nice code/features, but not all of
them are
- Original Message -
From: James pkx1...@gmail.com
To: pkx1...@gmail.com; tdanielsmu...@googlemail.com;
philehol...@googlemail.com; d...@gnu.org; lilypond-devel@gnu.org;
re...@codereview-hr.appspotmail.com
Sent: Wednesday, December 26, 2012 1:15 PM
Subject: Re: Doc: CG Clarifying about
First of all, a very Merry Christmas to you all.
Unfortunately I've had to spend the holidays in hospital, but I'm now a
much happier bunny now I have my notebook and have sorted out a mobile
broadband link.
I'm trying to prototype something so we can specify names and/or
suffixes for midi files
Le 25/12/2012 23:30, Francisco Vila disait :
El 25/12/2012 19:31, Federico Bruni escribió:
Il 25/12/2012 19:23, David Kastrup ha scritto:
What actually worries me is:
All other PO files for your package are available in:
http://translationproject.org/latest/lilypond/
And this shows:
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Catalan team of translators. The file is available at:
http://translationproject.org/latest/lilypond/ca.po
(We can arrange things so
LGTM
https://codereview.appspot.com/7013043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: benrg,
Message:
Actually, I didn't rewrite it - as the comment above suggests - this was
from Ben Rudiak-Gould.
I am helping him at least get some discussion review of his code
submission.
This patch has not been patchy-tested and I have just included
everything (i.e. also the .mid
Reviewers: zefram_fysh.org,
Message:
Issue 3062 - patch created by 'Zefram', but submitted by James
Description:
Report unterminated ties hanging at end of input
Issue 3062
LP doesn't report unterminated ties that are left hanging at the end
of input. Compare { a2~ r2 } (which warns) with {
Reviewers: zefram_fysh.org,
Message:
Patch submitted on behalf of zef...@fysh.org
Description:
canonicalise notional octave of tonic
Nothing deliberately looks at the octave part of the pitch object
storing
the tonic of a key-change event; it's not really a meaningful concept.
But comparison
Reviewers: zefram_fysh.org,
Message:
Submitted for zef...@fysh.org by James
Description:
Issue 3063
articulate grace notes with time stealing
This change makes \articulate handle grace notes itself, rendering them
to ordinary notes. There are a couple of tweakable parameters
controlling
the
LGTM.
https://codereview.appspot.com/7017044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hanwen - this has now 'push' status - in case you are not following the
tracker
http://code.google.com/p/lilypond/issues/detail?id=3044
https://codereview.appspot.com/6970046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the Catalan team of translators. The file is available at:
http://translationproject.org/latest/lilypond/ca.po
(We can arrange things so
23 matches
Mail list logo
