5
* Build a past revision from history:
7
- Working; now rebuild only up to a particular point.
9
- A generic test that can be applied to any test working directory
10
that all previous revisions can be successfully recreated.
12
* Ignore-file support: finalize design and then implement it.
14
* Command-line options: should be passed down as arguments to ``cmd``
17
- ``commit`` message should be an option, not an argument.
19
* Class representing a tree (or working directory or branch)
21
- Should this really be a class or is it better to just have a set
22
of global functions? What data is held in memory other than the
25
- List status and inventory sorted by file name.
27
- Add/move/delete files.
29
* Store patches in a zip file?
31
* When building diffs, show only the relevant tail of the two
32
filenames in the index line.
34
* Store patch headers in XML? What parser/generator to use? Maybe
35
tupletree-format, or Zope xmlpickle, or ElementTree_?
37
.. _ElementTree: http://effbot.org/zone/element-index.htm
39
* Make immutable files (e.g. recorded patches) read-only after they're
40
written. This would be a good idea, except that it means people
41
need to use ``rm -rf`` to remove branches, which may be dangerous.
47
* In the first instance, just cache everything; don't worry about
48
recreating them from simpler components. So keep a copy around of
49
all previous revisions, their inventory and manifest, etc.
51
* Start writing a test framework into which new development can fit.
53
* No need to handle move/rename or subdirectories yet.
55
* Do try to add assertions against invalid states.
57
* Keep it simple in interface and implementation.
added
removed
doc/work-order.txt
