On 02/08/2014 10:46 AM, Wang Shilong wrote:
From: Wang Shilong wangsl.f...@cn.fujitsu.com
This reverts commit 41ce9970a8a6a362ae8df145f7a03d789e9ef9d2.
Previously i was thinking we can use readonly root's commit root
safely while it is not true, readonly root may be cowed with the
following
On Sun, Feb 9, 2014 at 2:39 AM, Shilong Wang wangshilong1...@gmail.com wrote:
2014-02-08 23:46 GMT+08:00 Wang Shilong wangshilong1...@gmail.com:
From: Wang Shilong wangsl.f...@cn.fujitsu.com
This reverts commit 41ce9970a8a6a362ae8df145f7a03d789e9ef9d2.
Previously i was thinking we can use
2014-02-09 21:52 GMT+08:00 Filipe David Manana fdman...@gmail.com:
On Sun, Feb 9, 2014 at 2:39 AM, Shilong Wang wangshilong1...@gmail.com
wrote:
2014-02-08 23:46 GMT+08:00 Wang Shilong wangshilong1...@gmail.com:
From: Wang Shilong wangsl.f...@cn.fujitsu.com
This reverts commit
From: Wang Shilong wangsl.f...@cn.fujitsu.com
This reverts commit 41ce9970a8a6a362ae8df145f7a03d789e9ef9d2.
Previously i was thinking we can use readonly root's commit root
safely while it is not true, readonly root may be cowed with the
following cases.
1.snapshot send root will cow source
2014-02-08 23:46 GMT+08:00 Wang Shilong wangshilong1...@gmail.com:
From: Wang Shilong wangsl.f...@cn.fujitsu.com
This reverts commit 41ce9970a8a6a362ae8df145f7a03d789e9ef9d2.
Previously i was thinking we can use readonly root's commit root
safely while it is not true, readonly root may be
