http://bugs.grommit.com/show_bug.cgi?id=300
Vladimir.Marek at Sun.COM changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Vladimir.Marek at Sun.COM
------- Comment #1 from Vladimir.Marek at Sun.COM 2007-07-20 04:06 PDT -------
Copy & paste from the mailing list, this is description what wx backup does.
> 1. files in the active list including the SCCS s. and p. files (if the
> file is checked out).
> 2. The wx new list which is a wx state file that tracks newly created
> files in the workspace.
> 3. The wx renamed list (files that have been renamed in the workspace).
> 4. The wx sort_active state file (indicates user's preference in regards
> to wx keeping the active list sorted).
> 5. The wx *.NOT files which allow the user to record files which are
> exempt from certain wx putback checks like cstyle, etc...
> 6. The wx local_nametable file which is a subset of the local workspaces
> nametable containing the entries associated with the active, new and
> renamed lists.
>
> While generating this list I realize that wx should also backup the
> wx/backup_dir file but I haven't seen too many complaints about this so
> I'm not going to worry about it.
Other feature is, that restoring backup is not incremental, but absolute. That
means that you can do 'restore point1' then immediatelly 'restore point2' and
you are at 'point2'. You don't need to clean up the workspace in any way
between the restores.
>From the alias came few ideas about how to implement this
a) Similarly to current wx, store all modified files somewhere. That would have
to include some binary files from .hg.
b) Store difference against some common ancestor. Basically generate (git
style) patch.
c) Using MQ might provide similar functionality.
--
Configure bugmail: http://bugs.grommit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
