Re: Allura API

- Original Message - From: "Phil Holmes" To: Sent: Monday, August 31, 2015 4:10 PM Subject: Re: Allura API - Original Message - From: "Phil Holmes" To: Sent: Monday, August 31, 2015

Re: thinking twice about the new issue tracker

Il giorno gio 3 set 2015 alle 11:03, Trevor Daniels ha scritto: It works quite well. Status and labels are migrated correctly. Attachments are saved on Github server and displayed inline if they are images (Type-Ugly issues usually have image attachments). Are you

Re: thinking twice about the new issue tracker

Il giorno mer 2 set 2015 alle 18:52, Federico Bruni ha scritto: Il giorno mer 2 set 2015 alle 12:51, Federico Bruni ha scritto: I'm running the import on github. It takes more time, even if I've been whitelisted by github team. I'm currently at: Issue:

Re: Improve wording for an NR paragraph (issue 259710043 by simon.albre...@mail.de)

https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right): https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely#newcode3490 Documentation/notation/spacing.itely:3490: Or dynamics that

Re: thinking twice about the new issue tracker

Il giorno gio 3 set 2015 alle 11:07, David Kastrup ha scritto: "Trevor Daniels" writes: Federico, you wrote Thursday, September 03, 2015 9:24 AM It took about 10 hours. You can see the result here: https://github.com/fedelibre/lilyissues/issues

Re: Beautify Grob_array and stop using std::vector::data() (issue 264950043 by nine.fierce.ball...@gmail.com)

On 2015/09/02 23:27:41, Dan Eble wrote: If the sorting criterion uses attributes of the Grob that are changed by replacement, the array might not be sorted afterward (or might be sorted when it wasn't before). Grob_array does not appear to dictate the sorting criterion. So the routine

Re: thinking twice about the new issue tracker

Federico, you wrote Thursday, September 03, 2015 9:24 AM > It took about 10 hours. You can see the result here: > https://github.com/fedelibre/lilyissues/issues It's a pity you didn't do this a couple of months ago so we could have compared Github with Allura properly. It's a bit late now. >

Re: thinking twice about the new issue tracker

"Trevor Daniels" writes: > Federico, you wrote Thursday, September 03, 2015 9:24 AM > >> It took about 10 hours. You can see the result here: >> https://github.com/fedelibre/lilyissues/issues > > It's a pity you didn't do this a couple of months ago so we could > have

Re: thinking twice about the new issue tracker

Federico Bruni writes: > Github, unlike Bitbucket, does not put any restriction to the number > of contributors. And public repositories are free of charge. So IMO > this could have been a possible interim solution. "Free of charge" also means they reserve the right to dump

Re: thinking twice about the new issue tracker

Federico Bruni writes: > Il giorno gio 3 set 2015 alle 11:07, David Kastrup ha > scritto: >> "Trevor Daniels" writes: >> >>> Federico, you wrote Thursday, September 03, 2015 9:24 AM >>> It took about 10 hours. You can see the

Re: thinking twice about the new issue tracker

Federico Bruni wrote Thursday, September 03, 2015 10:21 AM > > Il giorno gio 3 set 2015 alle 11:03, Trevor Daniels > ha scritto: >> >>> It works quite well. Status and labels are migrated correctly. >>> Attachments are saved on Github server and displayed inline if they

Re: Improve wording for an NR paragraph (issue 259710043 by simon.albre...@mail.de)

Thanks for the input. https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely File Documentation/notation/spacing.itely (right): https://codereview.appspot.com/259710043/diff/1/Documentation/notation/spacing.itely#newcode3489

Small error in Allura issue import

Hello, I just came across a small error in the issue import: in the summary for , " <> " has been omitted. It’s present in the Google Code DB. I won’t fix this now, because we have no solution for the problem that all comments on the issue