---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4153/
---
(Updated Nov. 9, 2014, 1:56 a.m.)
Status
--
This change has been mark
On 8 November 2014 07:18, Olle E. Johansson wrote:
>
> On 28 Oct 2014, at 17:44, Russell Bryant
> wrote:
>
>
> I said this in my talk last week and will reiterate it here. I think the
> Asterisk dev community has been doing an amazing job over the last few
> years. Internal refactorings have b
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4157/
---
(Updated Nov. 8, 2014, 6 p.m.)
Status
--
This change has been marked
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4151/
---
(Updated Nov. 8, 2014, 1:29 p.m.)
Review request for Asterisk Developers.
---
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4152/
---
(Updated Nov. 8, 2014, 11:28 a.m.)
Status
--
This change has been mar
On 28 Oct 2014, at 17:44, Russell Bryant wrote:
>
> I said this in my talk last week and will reiterate it here. I think the
> Asterisk dev community has been doing an amazing job over the last few years.
> Internal refactorings have been achieved that we used to dream of. A new
> SIP cha
Den 2014-11-06 21:40, Matthew Jordan skrev:
On Wed, Nov 5, 2014 at 3:58 AM, Johan Wilfer wrote:
Den 2014-11-05 08:45, BJ Weschke skrev:
As for the timestamps for deciding whether the local cache is dirty
https://developers.google.com/web/fundamentals/performance/optimizing-content-efficienc
> On Nov. 6, 2014, 6:04 a.m., wdoekes wrote:
> > Isn't the better fix to disable coverage for the shadow compilation?
>
> Corey Farrell wrote:
> Probably. I have updated code but I won't have time to test until this
> weekend. I'll update the review once I've had a chance to do some build
