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%2Cwaiting&colspec=Patch%20
Owner%20ID%20Summary&sort=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 :
> Janek Warchoł: Patch: Set X-parent of TextScript to NoteColumn instead
> of PaperColumn
> http://code.google.com/p/lilypond/issues/detail?id=4005
It's
On 07/20/2014 11:47 AM, Janek Warchoł wrote:
2014-07-19 16:48 GMT+02:00 tisimst :
- 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"* ; music font
2014-07-19 12:59 GMT+02:00 David Kastrup :
> Thomas Morley 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 question is whether we will
Thomas Morley 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 master.
^
2014-07-21 11:34 GMT+02:00 David Kastrup :
> Thomas Morley 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
Thomas Morley writes:
> 2014-07-21 11:34 GMT+02:00 David Kastrup :
>>
>> 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 time, it appears to have c
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 `magni
Thanks for this! Some comments.
Cheers,
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/administra
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
Documentati
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 :
>>> - Question 1: *Should the new syntax be something like this?* (where
>>> the
>>> music and piano-brace fonts are put at the first)
>>>
>>> \paper {
>>>#(define fo
On 22. Juli 2014 07:51:00 MESZ, James 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 :
- Question 1: *Should the new syntax be something like this?*
>(where
the
music and piano-brace fonts ar
12 matches
Mail list logo
