On 2020/11/1 3:51, Gao Xiang wrote:
From: Gao Xiang
EROFS has _only one_ ondisk timestamp (ctime is currently
documented and recorded, we might also record mtime instead
with a new compat feature if needed) for each extended inode
since EROFS isn't mainly for archival purposes so no need to
kee
Hi Chao,
On Tue, Nov 03, 2020 at 11:58:42PM +0800, Chao Yu wrote:
> Hi Xiang,
>
> On 2020-11-3 10:50, Gao Xiang wrote:
> > Hi Chao,
> >
> > On Sun, Nov 01, 2020 at 03:51:02AM +0800, Gao Xiang wrote:
> > > From: Gao Xiang
> > >
> > > EROFS has _only one_ ondisk timestamp (ctime is currently
> >
Hi Xiang,
On 2020-11-3 10:50, Gao Xiang wrote:
Hi Chao,
On Sun, Nov 01, 2020 at 03:51:02AM +0800, Gao Xiang wrote:
From: Gao Xiang
EROFS has _only one_ ondisk timestamp (ctime is currently
documented and recorded, we might also record mtime instead
with a new compat feature if needed) for ea
Hi Chao,
On Sun, Nov 01, 2020 at 03:51:02AM +0800, Gao Xiang wrote:
> From: Gao Xiang
>
> EROFS has _only one_ ondisk timestamp (ctime is currently
> documented and recorded, we might also record mtime instead
> with a new compat feature if needed) for each extended inode
> since EROFS isn't mai
From: Gao Xiang
EROFS has _only one_ ondisk timestamp (ctime is currently
documented and recorded, we might also record mtime instead
with a new compat feature if needed) for each extended inode
since EROFS isn't mainly for archival purposes so no need to
keep all timestamps on disk especially fo
5 matches
Mail list logo