[Digikam-devel] [PATCH] Numbered Backups

[Nicolas Goutte]

On Wednesday 18 January 2006 22:05, David Faure wrote:
> On Tuesday 17 January 2006 21:35, Achim Bohnet wrote:
> > On Tuesday 17 January 2006 19:27, Tom Albers wrote:
> > > Op dinsdag 17 januari 2006 00:37, schreef Allen Winter:
> > > > Hi,
> > > >
> > > > Attached is a patch that provides numbered backups (eg. fred.~1~,
> > > > fred.~2~, ..., fred.~N~, where N is limited, default=10) in the
> > > > KSaveFile class.  It also renames the current backupFile() method to
> > > > simpleBackupFile() and then provides a new backupFile() method that
> > > > reads the user's global configfile for backup file parameters: the
> > > > backup type, the backup extension, and the max number of backups.
> > > >
> > > > Thus we could extend to other file backup schemes later, if desired.
> > > >
> > > > An idea that would compliment this very well, and also provide a very
> > > > cheap revision control method, is a File->Revert capability which
> > > > works as our typical file selector dialog, but filters on the backup
> > > > extension.
> > > >
> > > > For example, you are drawing in Krita.  You have 10 numbered backups
> > > > of that drawing.  You totally screw-up and want to revert back to an
> > > > older version.   Select File->Revert, and  file selection dialog
> > > > pop-ups with all 10 backups listed.  If you have preview on, you
> > > > could click each backup file, preview each drawing, then select which
> > > > one you'd like to revert to. Click <OK>.  Click <Yes> are sure you
> > > > want to revert?
> > > >
> > > > Anyhow, comments appreciated.
> >
> > I have not seen the patch, so I can't check, but I would like that
> > the first backup (assumed it's the original) never deleted.  So
> >
> > 	1st:	fred.orig
> > 	2nd:	name.~1~
> > 	3rd:	fred.~2~
> > 	etc
> >
> > This way one can _always_ go back and start from beginning of the
> > image manipulation even with a default of 1 (only keep orig version).
> > for space limited environments.
>
> This sounds strange to me.

As far as I have understood this kind of backup strategy, the idea is to have 
a .orig file from which you can always make a diff. Of course with SVN with 
its off-line diff, it is not necessary, but with e.g. CVS or without a 
version control it can be an interesting idea. (Probably it also helps to 
make small patches, which can be send to the corresponding software project.)

> If I have only one backup, it should be the last
> save, not the very first version of the file  (compare with text editors
> saving foo~ files).

A real ~ backup yes. But  the first file would be saved as *.orig in this kind 
of strategy.

>
> This is about the user saving, not about autosaves.

This is about to keep the unmodified file.

Have a nice day!