On Thu, May 21, 2009 at 11:13:34AM +0200, Joel Granados wrote: > On Wed, May 20, 2009 at 08:12:52PM -0400, Matt Davis wrote: > > What about the "history/save" feature? More or less, I threw together a few > > So this is something you would activate? Like calling parted with a > special argument so this get activated?
That would be advisable. However, it is enabled by default in that patch set I mentioned. > > patchset a while back, that did not perform any disk changes until a "save" > > command was issued. All of the commands to execute were queued, so that the > > Why use a queue? Why not use the parted internal structures (and not do > a commit like we currently do) but just change the internal structure. > After the user has given the save call disk.commit() IIRC That is what is done. However, its been quite some time since I have actually played with this patch set. I agree, using an internal container would be better. I appreciate your suggestions. > > user could undo/redo changes before committing to disk. > > > > http://lists.alioth.debian.org/pipermail/parted-devel/2007-November/002034.html > > This is a _very_ old patch 2007 :). Any plans to rebase it to current > git (next branch would be best)? Yes it is old. Not sure when I will be able to rebase it. Once again, I do appreciate your attention. -Matt _______________________________________________ parted-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/parted-devel
