From: Evert Mouw <post-yfx6isLFVcpeoWH0uzbU5w@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: time-shifting
Date: Mon, 08 Aug 2011 16:02:50 +0200 [thread overview]
Message-ID: <4E3FEC8A.3000303@evert.net> (raw)
In-Reply-To: <20110808.212859.255403671.ryusuke-sG5X7nlA6pw@public.gmane.org>
Hi,
Op 2011-08-08 14:28, Ryusuke Konishi schreef:
> [...]
> I agree with this let-it-be approach. [...] If the
> previous checkpoint number is lost, we only have to track back to the
> last valid checkpoint younger than it and confirm that the inode
> contained in the checkpoint is alive with the same generation number.
>
> Regards,
> Ryusuke Konishi
Totally cool.
Nice that it would be possible and workable. Maybe the idea can be put
in the todo list? I saw a one points on the todo list that might benefit
from this approach:
- Time slider
The time slider for a single file could be implemented by using the
proposed extra inode field "previous". (Another approach would be the
one currently employed by the TimeBrowse program.)
Keep up the good work!
Regards, Evert
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-08-08 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 7:38 time-shifting Evert Mouw
[not found] ` <4E3CEF72.1070303-yfx6isLFVcpeoWH0uzbU5w@public.gmane.org>
2011-08-07 14:19 ` time-shifting Ryusuke Konishi
[not found] ` <20110807.231959.212685724.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-08-07 22:17 ` time-shifting Evert Mouw
[not found] ` <4E3F0F16.7020200-yfx6isLFVcpeoWH0uzbU5w@public.gmane.org>
2011-08-08 12:28 ` time-shifting Ryusuke Konishi
[not found] ` <20110808.212859.255403671.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-08-08 14:02 ` Evert Mouw [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3FEC8A.3000303@evert.net \
--to=post-yfx6islfvcpeowh0uzbu5w@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).