Added to Tracker:
https://code.google.com/p/lilypond/issues/detail?id=1873
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Wed, 7 Sep 2011 11:17:59 +0100, Graham Percival wrote:
We have now reached 0 Critical issues. It would be great if we
could verify the fixed issues, and if we could find out if
anything broke in 2.15.10.
Once that's done, I'll go ahead with release candidate 2,
hopefully in a few days. Then
Hello,
I've had a brief conversation with Graham who agreed in principle and
asked me to send a mail to dev regarding 'going through' and 'cleaning
up' old tracker issues.
At the moment we have 580-something tracker issues of which some
haven't been 'touched' for a very long time, there are also
> However this will probably generate a fair few auto-emails and I
> don't want to step on anyone else's toes such as other
> tracker-sniffers (Messrs Campbell and O. Redchuk). So I am running
> this pass the 'dev' group for any other additional suggestions (such
> as other labels I could remove/
LGTM
http://codereview.appspot.com/4956062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, Sep 08, 2011 at 10:10:18AM +0300, m...@apollinemike.com wrote:
> On Wed, 7 Sep 2011 11:17:59 +0100, Graham Percival wrote:
> >We have now reached 0 Critical issues. It would be great if we
> >could verify the fixed issues, and if we could find out if
> >anything broke in 2.15.10.
>
> Just
Hi James (or is it Peekay now! ;)
I've had a brief conversation with Graham who agreed in principle
and
asked me to send a mail to dev regarding 'going through' and
'cleaning
up' old tracker issues.
Good idea!
However this will probably generate a fair few auto-emails and I
don't
want to
On Thu, Sep 08, 2011 at 08:25:25AM +0100, Peekay Ex wrote:
>
> 1) Remove erroneous 'Owner' and 'Status' labels (and CC if appropriate).
The status should almost always be Accepted. If the Owner is me
or Valentin, that should be removed (it was an artifact of an old
system) unless the issue has a
On Thu 08 Sep 2011, 09:53 Graham Percival wrote:
> Yes. Please add "bug still in 2.15.10" in those cases. If the
> graphical output has changed, also add a png.
> Dmytro has a very nice script that produces better pngs -- some of
> the old reports have a pdf; please replace that with a png.
Dmytr
Looks very promising.
A couple of style comments.
I think the naming should be revised to include Kievan as part of the
name, at least for the notes like s1.
Thanks,
Carl
http://codereview.appspot.com/4951062/diff/1/mf/feta-kievan.mf
File mf/feta-kievan.mf (right):
http://codereview.appspo
On 11-09-08 01:25 AM, Peekay Ex wrote:
Hello,
I've had a brief conversation with Graham who agreed in principle and
asked me to send a mail to dev regarding 'going through' and 'cleaning
up' old tracker issues.
At the moment we have 580-something tracker issues of which some
haven't been 'touch
2011/9/8 Aleksandr Andreev :
> Hi folks,
>
> So now that we've got the Metafont code for the Kievan glyphs, what
> shall I do next?
>
> Basically, I would like to have an interface for Kievan Notation that
> achieves the following:
> 1. Automatically uses the Kievan tsefaut clef.
> 2. Suppresses Ti
Well, I tried pushing a multi-commit change as a single merge commit
right now. The idea behind this was that the last commit in the
sequence was getting most of the testing attention, and usually nobody
will gain from bisecting possibly suboptimal commits in the sequence (I
did try to make reaso
> d) "Translation of GIT committish: xxx". Uh. What to put into
> "committish"? Likely the merge commit.
Or the last commit in the history of the original file which this is a
translation of. It is well known by looking at the fisrt line of git log
the_file.
_
Francisco Vila writes:
>> d) "Translation of GIT committish: xxx". Uh. What to put into
>> "committish"? Likely the merge commit.
>
> Or the last commit in the history of the original file which this is
> a translation of. It is well known by looking at the fisrt line of git
> log the_fil
Hi all,
What happened with the bug report about the problem with TAB using a
quarter-tone scordatura?
I remember I did spend a good time trying to isolate the problem, but
I can't find it anymore in the bug tracker.
Any news on this issue?
___
lilypond
Just found:
http://code.google.com/p/lilypond/issues/detail?id=1741&can=1&q=tablature&colspec=ID%20Type%20Status%20Stars%20Owner%20Patch%20Needs%20Summary
The correct description would be:
"Tablature Bug when pitch is higher then beh in a quarter-tone string "
__
Anyway, anyone has a hint about this issue?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, Sep 08, 2011 at 04:12:04PM +0200, David Kastrup wrote:
>
> Well, I tried pushing a multi-commit change as a single merge commit
> right now.
Thanks for the experiment! This is useful information for a
long-away GOP proposal
http://lilypond.org/~graham/gop/gop_19.html
(currently "GOP h -
> I think it should be done similarly to ancient music support: add a
> new kind of context, for example KievanVoice.
> See how mensural notation works now - an example:
OK, so IIUC, I have to add code to engraver-init.ly, and I can use the
MensuralVoice context as an example. That seems to be fa
2011/9/8 David Kastrup :
>
> Well, I tried pushing a multi-commit change as a single merge commit
> right now. The idea behind this was that the last commit in the
> sequence was getting most of the testing attention, and usually nobody
> will gain from bisecting possibly suboptimal commits in the
Am Donnerstag, 8. September 2011, 22:11:45 schrieb Aleksandr Andreev:
> > I think it should be done similarly to ancient music support: add a
> > new kind of context, for example KievanVoice.
>
> > See how mensural notation works now - an example:
> OK, so IIUC, I have to add code to engraver-init
passes make and reg tests
http://codereview.appspot.com/4950071/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham Percival writes:
> On Thu, Sep 08, 2011 at 04:12:04PM +0200, David Kastrup wrote:
>>
>> Well, I tried pushing a multi-commit change as a single merge commit
>> right now.
>
> Thanks for the experiment! This is useful information for a
> long-away GOP proposal
> http://lilypond.org/~graha
El 08/09/2011 19:22, "David Kastrup" escribió:
>
> Francisco Vila writes:
>
> >> d) "Translation of GIT committish: xxx". Uh. What to put into
> >> "committish"? Likely the merge commit.
> >
> > Or the last commit in the history of the original file which this is
> > a translation of. It is w
http://codereview.appspot.com/4951062/diff/1/mf/feta-kievan.mf
File mf/feta-kievan.mf (right):
http://codereview.appspot.com/4951062/diff/1/mf/feta-kievan.mf#newcode78
mf/feta-kievan.mf:78: fill z1{dir -6.9} .. z2 .. z3 & z3 .. z4 .. z5 &
z5 -- z6 & z6 .. z7 .. z8 & z8{left} .. z9 & z9 .. z10 ..
26 matches
Mail list logo
