Fixed. Thanks for review!
https://codereview.appspot.com/118950043/diff/1/scm/define-grob-properties.scm
File scm/define-grob-properties.scm (right):
https://codereview.appspot.com/118950043/diff/1/scm/define-grob-properties.scm#newcode814
scm/define-grob-properties.scm:814: Value
Hi,
2014-07-20 16:43 GMT+02:00 Abraham Lee tisi...@gmail.com:
On Sun, Jul 20, 2014 at 3:47 AM, Janek Warchoł janek.lilyp...@gmail.com
wrote:
A thought: i'm missing the possibility to set the weight of the music font
used by LilyPond for a particular score. In other words: let's
say i have
Hello,
Here is the current patch countdown list. The next countdown will be on
July 24th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaitingcolspec=Patch%20
Owner%20ID%20Summarysort=patch
Hello,
since the list of patches to review is short this time, i'm moving
this one from review to countdown:
2014-07-21 9:01 GMT+02:00 James james.l...@outlook.com:
Janek Warchoł: Patch: Set X-parent of TextScript to NoteColumn instead
of PaperColumn
On 07/20/2014 11:47 AM, Janek Warchoł wrote:
2014-07-19 16:48 GMT+02:00 tisimst tisi...@gmail.com:
- Question 1: *Should the new syntax be something like this?* (where the
music and piano-brace fonts are put at the first)
\paper {
#(define fonts
(make-pango-font-tree
*lilyjazz* ;
2014-07-19 12:59 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
Hi,
because of that unwanted merge while the patch for issue 3992 was
pushed, i'm not sure what to do with my own patch for issue 4008.
Should I wait before I push myself?
If the
Thomas Morley thomasmorle...@gmail.com writes:
If it isn't, we'll walk through any problems. The CG recipe cited is
not really helpful there. Personally, I just do
git fetch
git rebase origin/master mybranch
git push origin HEAD:staging
This will refuse pushing when staging is ahead of
2014-07-21 11:34 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
If it isn't, we'll walk through any problems. The CG recipe cited is
not really helpful there. Personally, I just do
git fetch
git rebase origin/master mybranch
git push origin
Thomas Morley thomasmorle...@gmail.com writes:
2014-07-21 11:34 GMT+02:00 David Kastrup d...@gnu.org:
You are perfectly fine here. However, origin/staging is _not_ listed
here as a reference: it has indeed moved ahead so that, like I stated,
git refuses to push.
At the current point of
markpolesky wrote
Regarding the naming, looks like it's a tie between `resize' and
`magnify', with `magnify' slightly ahead if you count Paul's vote as
split:
scale: Paul
resize: Paul, Marc
magnify: James, David N.
Unless there's more opposition, I'll probably push it as `magnify'; we
Thanks for this! Some comments.
Cheers,
Julien
https://codereview.appspot.com/112280043/diff/20001/Documentation/contributor/administration.itexi
File Documentation/contributor/administration.itexi (right):
Thanks Julien
https://codereview.appspot.com/112280043/diff/20001/Documentation/contributor/administration.itexi
File Documentation/contributor/administration.itexi (right):
https://codereview.appspot.com/112280043/diff/20001/Documentation/contributor/administration.itexi#newcode161
On 21/07/14 09:46, Alexander Kobel wrote:
On 07/20/2014 11:47 AM, Janek Warchoł wrote:
2014-07-19 16:48 GMT+02:00 tisimst tisi...@gmail.com:
- Question 1: *Should the new syntax be something like this?* (where
the
music and piano-brace fonts are put at the first)
\paper {
#(define fonts
On 22. Juli 2014 07:51:00 MESZ, James pkx1...@gmail.com wrote:
On 21/07/14 09:46, Alexander Kobel wrote:
On 07/20/2014 11:47 AM, Janek Warchoł wrote:
2014-07-19 16:48 GMT+02:00 tisimst tisi...@gmail.com:
- Question 1: *Should the new syntax be something like this?*
(where
the
music and
14 matches
Mail list logo
