Re: [Bf-committers] 2.79a release - proposed list of commits

2017-12-27 Thread Bastien Montagne
I just happen to have finished gathering add-ons commits and send the list to bf-python ;) Le 27/12/2017 à 15:52, Julien Duroure a écrit : Hello, Seems this list doesn't include addon repo commits. Is there somewhere a list of commit to backport for addons ? Thinking about Rigify commits for

Re: [Bf-committers] 2.79a release - proposed list of commits

2017-12-27 Thread Gaia Clary
hi. I believe this one (Collada - crash during export) should be added: rB1f95347882 ( Fix T53322 ) But maybe Campbell should decide. cheers, Gaia On 27.12.2017 12:05, Bastien Montagne wrote: So… looks like our list of commits to backport is too long, even the ML server does not want to

Re: [Bf-committers] 2.79a release - proposed list of commits

2017-12-27 Thread Julien Duroure
Hello, Seems this list doesn't include addon repo commits. Is there somewhere a list of commit to backport for addons ? Thinking about Rigify commits for example. Cheers, Julien On Wed, Dec 27, 2017 at 12:14 PM, Sybren A. Stüvel wrote: > On 27/12/17 12:05, Bastien Montagne

Re: [Bf-committers] 2.79a release - proposed list of commits

2017-12-27 Thread Sybren A . Stüvel
On 27/12/17 12:05, Bastien Montagne wrote: > First part are commits we think should be included, please > double-check yours though. > [...] You may also suggest other commit of course, just keep in mind > that we want only fixes I would like to see this commit in 2.79a too. I think it's a farily

[Bf-committers] 2.79a release - proposed list of commits

2017-12-27 Thread Bastien Montagne
So… looks like our list of commits to backport is too long, even the ML server does not want to swallow it. :) Here is the list we gathered, Sergey and I: http://pasteall.org/737326 First part are commits we think should be included, please double-check yours though. Second part are commits

[Bf-committers] No IRC for me

2017-12-27 Thread Bastien Montagne
Hey guys, Since yesterday 8pm, I cannot connect to freenode at all (getting a cryptic "Notice -- You need to identify via SASL to use this server")… From some googling, it could be related to recent spambots attacks maybe? Anyway, just so that you know (and hopping this gets fixed soon).