Hi David, 2017-02-15 0:25 GMT+01:00 David Nalesnik <[email protected]>: > Hi Harm, > > On Thu, Feb 9, 2017 at 8:10 AM, David Nalesnik <[email protected]> > wrote: >> On Wed, Feb 8, 2017 at 3:46 PM, Thomas Morley <[email protected]> >> wrote: >>> 2017-02-08 14:37 GMT+01:00 David Nalesnik <[email protected]>: >>> >>>> I notice that the patch has gotten swept up into the review process. >>>> If you like, I will tell James to remove it, or maybe put it into >>>> waiting so I can figure out how to fix my machine? (It's already >>>> gotten a review!) I don't want to put you or anybody to extra trouble. >>> >> >> Hi Harm, >> >>> >>> Hi David, >>> >>> I'd happily shepherd this issue. >>> It would be a pitty to waste the already started review. >>> >>> I doubt I can help figuring out whats wrong with your VB, though, if >>> you think I can check/test anything from my end, please shout. >>> >> >> Thanks--I appreciate this! I'll wait to collect a good number of >> review comments before submitting any updates. >> > > OK--I've made a patch update based on the review comments so far. > (See attachment.)
I'll upload it asap, which will likely be tomorrow evening. > Maybe the solution to the problem is to scrap Win10 altogether. The > insidious updates seem to have messed up my permissions, so I can't > update VirtualBox -- even running the installer as an administrator. > (Was hoping that a newer version would correct the problem I'm > having.) Sorry to hear that. Some time ago I used a dual boot setup. After all I hear from Win 10 updates, I'm very happy I dropped windows entirely. Cheers, Harm _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
