71
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
72
giving options to display ids, types, etc.
74
* Atomic file class that renames into place when it's closed.
76
* Don't abort if ``~/.bzr.log`` can't be used.
78
74
* Split BzrError into various more specific subclasses for different
79
75
errors people might want to catch.
89
85
immutable and which can vary. On the other hand, it's much simpler
90
86
to just use an external proxy cache.
88
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
89
~/.arch-cache, containing revision information encoded almost as a
90
bunch of archives. Perhaps we could simply store full paths.
92
92
* Maybe also store directories in the statcache so that we can quickly
93
93
identify that they still exist.
95
* Diff should show timestamps; for files from the working directory we
96
can use the file itself; for files from a revision we should use the
97
commit time of the revision.
99
* Perhaps split command infrastructure from the actual command
102
* Cleaner support for negative boolean options like --no-recurse.
104
* Statcache should possibly map all file paths to / separators
106
* quotefn doubles all backslashes on Windows; this is probably not the
107
best thing to do. What would be a better way to safely represent
108
filenames? Perhaps we could doublequote things containing spaces,
109
on the principle that filenames containing quotes are unlikely?
110
Nice for humans; less good for machine parsing.
112
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
115
* Branch.update_revisions() inefficiently fetches revisions from the
116
remote server twice; once to find out what text and inventory they
117
need and then again to actually get the thing. This is a bit
120
One complicating factor here is that we don't really want to have
121
revisions present in the revision-store until all their constituent
122
parts are also stored.
124
The basic problem is that RemoteBranch.get_revision() and similar
125
methods return object, but what we really want is the raw XML, which
126
can be popped into our own store. That needs to be refactored.
128
* ``bzr status FOO`` where foo is ignored should say so.
130
* ``bzr mkdir A...`` should just create and add A.
99
* Change command functions into Command() objects, like in hct, and
100
then the grammar can be described directly in there. Since all
101
option definitions are global we can define them just once and
102
reference them from each command.
104
* Merge Aaron's merge code.
106
137
* Merge revert patch.
108
139
* ``bzr mv`` that does either rename or move as in Unix.
117
148
* Fix up Inventory objects to represent root object as an entry.
119
* Don't convert entire entry from
150
* Don't convert entire entry from ElementTree to an object when it is
151
read in, but rather wait until the program actually wants to know
121
154
* Extract changes from one revision to the next to a text form
122
155
suitable for transmission over email.
131
164
* Write a reproducible benchmark, perhaps importing various kernel versions.
133
* Change test.sh from Bourne shell into something in pure Python so
134
that it can be more portable.
136
166
* Directly import diffs! It seems a bit redundant to need to rescan
137
167
the directory to work out what files diff added/deleted/changed when
138
168
all the information is there in the diff in the first place.
248
278
urlgrabber's docs say they are working on batched downloads; we
249
279
could perhaps ride on that or just create a background thread (ew).
251
* Should be a signature at the top of the cache file.
253
281
* Paranoid mode where we never trust SHA-1 matches.
255
283
* Don't commit if there are no changes unless forced.
257
* --dry-run mode for commit?
285
* --dry-run mode for commit? (Or maybe just run with
286
check-command=false?)
259
288
* Generally, be a bit more verbose unless --silent is specified.
290
* Function that finds all changes to files under a given directory;
291
perhaps log should use this if a directory is given.
293
* XML attributes might have trouble with filenames containing \n and
294
\r. Do we really want to support this? I think perhaps not.
296
* Remember execute bits, so that exports will work OK.
298
* Unify smart_add and plain Branch.add(); perhaps smart_add should
299
just build a list of files to add and pass that to the regular add
302
* Function to list a directory, saying in which revision each file was
303
last modified. Useful for web and gui interfaces, and slow to
304
compute one file at a time.
306
* unittest is standard, but the results are kind of ugly; would be
307
nice to make it cleaner.
309
* Check locking is correct during merge-related operations.
311
* Perhaps attempts to get locks should timeout after some period of
312
time, or at least display a progress message.
314
* Split out upgrade functionality from check command into a separate
293
349
files, and respecting selective commits. Run the pre-commit check
294
350
(e.g. compile and run test suite) in there.
352
Possibly this should be done by splitting the commit function into
353
several parts (under a single interface). It is already rather
354
large. Decomposition:
356
- find tree modifications and prepare in-memory inventory
358
- export that inventory to a temporary directory
360
- run the test in that temporary directory
362
- if that succeeded, continue to actually finish the commit
364
What should be done with the text of modified files while this is
365
underway? I don't think we want to count on holding them in memory
366
and we can't trust the working files to stay in one place so I
367
suppose we need to move them into the text store, or otherwise into
368
a temporary directory.
370
If the commit does not actually complete, we would rather the
371
content was not left behind in the stores.
298
375
* GUI (maybe in Python GTK+?)
added
removed
TODO
