On Sun, Jul 24, 2011 at 9:40 PM, Graham Percival
wrote:
> I believe that the first step to investigating this problem is to
> find the google code tracker for google code, and either add this
> issue there, or read the existing material if there is one.
Unofficial:
http://code.google.com/p/google
On Sun, Jul 24, 2011 at 08:28:45PM +0100, Trevor Daniels wrote:
>
> Well, in this particular case it would have saved
> me an hour's work.
I agree that there is a problem here.
I believe that the first step to investigating this problem is to
find the google code tracker for google code, and eit
Phil Holmes wrote Sunday, July 24, 2011 7:09 PM
From: "Trevor Daniels"
I still don't see the problem. If you want to see just
the fixed issues to verify, can't you search for
Issues to verify with Status: Fixed ?
It seems to work fine. I changed 868 back to
Duplicate to test it. That w
On Sun, Jul 24, 2011 at 06:00:24PM +0100, Phil Holmes wrote:
> - Original Message - From: "Trevor Daniels"
>
> >>I was simply verifying that it's a duplicate - when issues are
> >>merged they
> >>stay on the "Issues to verify" list unless this is done.
> >
> >That seems misleading.
>
> I'
- Original Message -
From: "Trevor Daniels"
To: "Graham Percival" ; "Phil Holmes"
Cc: "Lily-Devel List"
Sent: Sunday, July 24, 2011 6:55 PM
Subject: Re: Issue 868 in lilypond: \parenthesize does not
takedottednotesinto account
Graham Perc
Graham Percival wrote Sunday, July 24, 2011 6:15 PM
Trevor: I agree that this is misleading. I would **love** to be
able to configure our tracker page to say "these tags indicate
that an issue should not appear on the 'issues to verify' list".
I still don't see the problem. If you want to s
- Original Message -
From: "Trevor Daniels"
To: "Lily-Devel List" ; "Phil Holmes"
Sent: Sunday, July 24, 2011 5:51 PM
Subject: Re: Issue 868 in lilypond: \parenthesize does not
takedottednotesinto account
Phil Holmes wrote:
"Trevor Daniels&
Phil Holmes wrote:
"Trevor Daniels" wrote in message
I don't see a commit that purports to fix this issue,
nor is one referenced in the bug report.
Have I missed it? Are you sure this is verified?
Trevor
I was simply verifying that it's a duplicate - when issues are
merged they
stay o
