On Tue, Sep 27, 2016 at 04:29:07PM +0200, Michal Privoznik wrote:
On 23.09.2016 15:20, Martin Kletzander wrote:
If this reminds you of a commit message from around a year ago, it's
41c2aa729f0af084ede95ee9a06219a2dd5fb5df and yes, we're dealing with
"the same thing" again. Or f309db1f4d51009bad
On Wed, Sep 28, 2016 at 12:00:22PM +1000, Sam Bobroff wrote:
On Fri, Sep 23, 2016 at 03:20:56PM +0200, Martin Kletzander wrote:
If this reminds you of a commit message from around a year ago, it's
41c2aa729f0af084ede95ee9a06219a2dd5fb5df and yes, we're dealing with
"the same thing" again. Or f3
On Fri, Sep 23, 2016 at 03:20:56PM +0200, Martin Kletzander wrote:
> If this reminds you of a commit message from around a year ago, it's
> 41c2aa729f0af084ede95ee9a06219a2dd5fb5df and yes, we're dealing with
> "the same thing" again. Or f309db1f4d51009bad0d32e12efc75530b66836b and
> it's similar.
On 23.09.2016 15:20, Martin Kletzander wrote:
> If this reminds you of a commit message from around a year ago, it's
> 41c2aa729f0af084ede95ee9a06219a2dd5fb5df and yes, we're dealing with
> "the same thing" again. Or f309db1f4d51009bad0d32e12efc75530b66836b and
> it's similar.
>
> There is a logi
If this reminds you of a commit message from around a year ago, it's
41c2aa729f0af084ede95ee9a06219a2dd5fb5df and yes, we're dealing with
"the same thing" again. Or f309db1f4d51009bad0d32e12efc75530b66836b and
it's similar.
There is a logic in place that if there is no real need for
memory-backen
