From 64c97de5be7f899e1d36e620b3a5959d122909c7 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Sun, 9 Oct 2016 20:29:04 -0700 Subject: Renamed timefsN examples to fuse_notify_* This should make it more obvious at first glance what the different examples do. --- ChangeLog.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) (limited to 'ChangeLog.rst') diff --git a/ChangeLog.rst b/ChangeLog.rst index e029cd6..da1b1a8 100644 --- a/ChangeLog.rst +++ b/ChangeLog.rst @@ -5,13 +5,12 @@ Unreleased Changes for unknown reasons -- maybe because it tries to treat the mountpoint as a file rather than a directory? -* There is a new ``timefs3`` example that demonstrates the use of - `fuse_lowlevel_notify_inval_entry`. +* There are several new examples that demonstrate the use of + the ``fuse_lowlevel_notify_*`` functions: -* There are new ``timefs1`` and ``timefs2`` examples that demonstrate - the use of the `fuse_lowlevel_notify_store`, - `fuse_lowlevel_notify_retrieve`, and - `fuse_lowlevel_notify_inval_inode` functions. + - ``example/notify_store_retrieve.c`` + - ``example/notify_inval_inode.c`` + - ``example/notify_inval_entry.c`` * The ``-o big_writes`` mount option has been removed. It is now always active. File systems that want to limit the size of write -- cgit v1.2.3