Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	mniederle-RbZlAiThDcE@public.gmane.org
Subject: Re: Discard Changes
Date: Fri, 12 Jun 2009 13:05:58 +0900 (JST)	[thread overview]
Message-ID: <20090612.130558.21013146.ryusuke@osrg.net> (raw)
In-Reply-To: <20090611083413.1f18a0eb@simplux>

Hi,
On Thu, 11 Jun 2009 08:34:13 +0200, "Dipl.-Ing. Michael Niederle" wrote:
> Hi!
> 
> I found the item "checkpoint rollback" in the todo-list. By "checkpoint
> rollback" you mean discarding all changes since a given checkpoint?

Yes, exactly.
 
> Such a feature would be *very* nice! I can't imagine that it should be very
> complicated to implement, but I might be wrong.
> 
> In SIMPLUX (a live distribution) users shall have a chance to abolisch
> all changes made in a session. So I would create a snapshot at each startup and
> remove all checkpoints created afterwards to revert to the previous state if
> user decides to do so.
> 
> Greetings, Michael

I imagine it is likely be compilcated in NILFS because a few metadata
files have no past versions in the current implementation.

Nilfs can change checkpoints to snapshots in later.  So, I think the
rollback feature should inherit this characteristics.  That is,
rollback without a prior make-snapshot operation.

Cheers,
Ryusuke Konsihi

      reply	other threads:[~2009-06-12  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1244516401.12212.users@nilfs.org>
     [not found] ` <mailman.1.1244516401.12212.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
2009-06-11  6:34   ` Discard Changes Dipl.-Ing. Michael Niederle
2009-06-12  4:05     ` Ryusuke Konishi [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=20090612.130558.21013146.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=mniederle-RbZlAiThDcE@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@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