Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

Op vrijdag 17 augustus 2007, schreef Wilbert Berendsen: > What did I do wrong? (still newbee with git...) now I did git checkout origin/master instead of git checkout master and that gave me the more recent logs and files. Is that the correct way? :) with best regards, Wilbert Berendsen -- htt

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

Op vrijdag 17 augustus 2007, schreef Joe Neeman: > That's strange because I merged jneeman into master a little while ago. > Does 'git log master' show that commit 2a6bf54a5ebf426 is part of master? somehow git log master|grep 2a6bf54a5ebf426 shows nothing. I did git-checkout master and git-pull b

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

On Thursday 16 August 2007 08:19, Wilbert Berendsen wrote: > Op dinsdag 7 augustus 2007, schreef Joe Neeman: > > Does the problem still exist in the jneeman branch of git? If it does, > > I'd be particularly interested in seeing examples with stems in the wrong > > order. > > git master as of today

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

Op donderdag 16 augustus 2007, schreef Wilbert Berendsen: > after that I tested the jneeman branch of my file I meant "I tested the jneeman branch on my file" :-) w best regards, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ "You must be the change you wish to see in the world."

Re[2]: kneed spacing too tight, as of git 4 august (recently introduced regression)

Op dinsdag 7 augustus 2007, schreef Joe Neeman: > Does the problem still exist in the jneeman branch of git? If it does, I'd > be particularly interested in seeing examples with stems in the wrong > order. git master as of today still shows the same too tight spacing choice as in my previous mail

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

Op dinsdag 7 augustus 2007, schreef Joe Neeman: > On Monday 06 August 2007 16:33, Wilbert Berendsen wrote: > > %{ > > LilyPond chooses too tight spacing: the stems of kneed notes are too > > close and the spacing too tight. This also occurs in one of my larger > > projects, where the stems even are

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

Hello, Joe wrote: Does the problem still exist in the jneeman branch of git? If it does, I'd be particularly interested in seeing examples with stems in the wrong order. Sorry, I'm on holiday right now, I cant't use git from this pc... will check next week, when I'm home! Best regards, Wilbe

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

Hello Joe, can you look into fixing this problem, and merging the fixes into master? Due to time-pressure, I don't want to delay 2.11.29 any further, but shipping it breaks one of the major rules for lilypond development: every release should be strictly better than the preceding one. thanks, 2

Re: kneed spacing too tight, as of git 4 august (recently introduced regression)

On Monday 06 August 2007 16:33, Wilbert Berendsen wrote: > %{ > LilyPond chooses too tight spacing: the stems of kneed notes are too close > and the spacing too tight. This also occurs in one of my larger projects, > where the stems even are in the wrong order and sometimes outside the > beams. It

kneed spacing too tight, as of git 4 august (recently introduced regression)

%{ LilyPond chooses too tight spacing: the stems of kneed notes are too close and the spacing too tight. This also occurs in one of my larger projects, where the stems even are in the wrong order and sometimes outside the beams. It seems that the optical spacing of kneed beamed notes (put stems a