On Aug 7, 2011, at 1:35 AM, Keith OHara wrote:
mike at apollinemike.com mike at apollinemike.com writes:
I'm getting a lot of circular dependencies for
input/regression/beam-skip.ly from the current master.
I don't have time to do a full git bisect, but is this
standard behavior?
mike at apollinemike.com mike at apollinemike.com writes:
I'm getting a lot of circular dependencies for
input/regression/beam-skip.ly from the current master.
I don't have time to do a full git bisect, but is this
standard behavior?
You should have a word with the gentleman who pushed
Hey all,
I'm getting a lot of circular dependencies for input/regression/beam-skip.ly
from the current master. I don't have time to do a full git bisect, but is
this standard behavior?
Cheers,
MS
___
lilypond-devel mailing list
Mike,
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of m...@apollinemike.com
)Sent: 13 July 2011 07:58
)To: lilypond-devel@gnu.org List
)Subject: Circular dependencies for beam
-devel@gnu.org List
)Subject: Circular dependencies for beam-skip.ly
)
)Hey all,
)
)I'm getting a lot of circular dependencies for input/regression/beam-
)skip.ly from the current master. I don't have time to do a full git bisect,
)but is this standard behavior?
)
See
http
Mike,
)-Original Message-
)From: m...@apollinemike.com [mailto:m...@apollinemike.com]
)Sent: 13 July 2011 11:14
)To: James Lowe
)Cc: lilypond-devel@gnu.org List
)Subject: Re: Circular dependencies for beam-skip.ly
)Importance: Low
)
)On Jul 13, 2011, at 12:12 PM, James Lowe wrote
On Jul 13, 2011, at 12:19 PM, James Lowe wrote:
Mike,
)-Original Message-
)From: m...@apollinemike.com [mailto:m...@apollinemike.com]
)Sent: 13 July 2011 11:14
)To: James Lowe
)Cc: lilypond-devel@gnu.org List
)Subject: Re: Circular dependencies for beam-skip.ly
)Importance
On 13 July 2011 11:22, m...@apollinemike.com m...@apollinemike.com wrote:
You're right - they would have been the same. I think this error may have
been introduced in a recent patch, in which case it is a regression. I'd
have to run git-bisect to figure it out, though, but all of my CPU is
On Jul 13, 2011, at 9:37 PM, Neil Puttock wrote:
On 13 July 2011 11:22, m...@apollinemike.com m...@apollinemike.com wrote:
You're right - they would have been the same. I think this error may have
been introduced in a recent patch, in which case it is a regression. I'd
have to run
On 13 July 2011 20:51, m...@apollinemike.com m...@apollinemike.com wrote:
Was I too narrow in my original fix? I can work on something cleaner to
address the segfault that doesn't lead to cyclical dependencies so that this
doesn't perturb future generations of regtests.
That would be
On 13 July 2011 21:03, Neil Puttock n.putt...@gmail.com wrote:
On 13 July 2011 20:51, m...@apollinemike.com m...@apollinemike.com wrote:
Was I too narrow in my original fix? I can work on something cleaner to
address the segfault that doesn't lead to cyclical dependencies so that this
On Jul 13, 2011, at 10:09 PM, Neil Puttock wrote:
On 13 July 2011 21:03, Neil Puttock n.putt...@gmail.com wrote:
On 13 July 2011 20:51, m...@apollinemike.com m...@apollinemike.com wrote:
Was I too narrow in my original fix? I can work on something cleaner to
address the segfault that
12 matches
Mail list logo
