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.
74
78
* Split BzrError into various more specific subclasses for different
75
79
errors people might want to catch.
81
85
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
87
* testbzr should by default test the bzr binary in the same directory
88
as the testbzr script, or take a path to it as a first parameter.
90
Should show the version from bzr and the path name.
83
92
* RemoteBranch could maintain a cache either in memory or on disk. We
84
93
know more than an external cache might about which files are
85
94
immutable and which can vary. On the other hand, it's much simpler
86
95
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
97
* Maybe also store directories in the statcache so that we can quickly
93
98
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. (?)
104
* Change command functions into Command() objects, like in hct, and
105
then the grammar can be described directly in there. Since all
106
option definitions are global we can define them just once and
107
reference them from each command.
109
* Selective commit of only some files.
111
* Merge Aaron's merge code.
119
113
* Merge revert patch.
121
115
* ``bzr mv`` that does either rename or move as in Unix.
130
124
* Fix up Inventory objects to represent root object as an entry.
132
* Don't convert entire entry from ElementTree to an object when it is
133
read in, but rather wait until the program actually wants to know
126
* Don't convert entire entry from
136
128
* Extract changes from one revision to the next to a text form
137
129
suitable for transmission over email.
139
131
* More test cases.
141
- Selected-file commit
143
- Impossible selected-file commit: adding things in non-versioned
144
directories, crossing renames, etc.
146
133
* Write a reproducible benchmark, perhaps importing various kernel versions.
135
* Change test.sh from Bourne shell into something in pure Python so
136
that it can be more portable.
148
138
* Directly import diffs! It seems a bit redundant to need to rescan
149
139
the directory to work out what files diff added/deleted/changed when
150
140
all the information is there in the diff in the first place.
260
250
urlgrabber's docs say they are working on batched downloads; we
261
251
could perhaps ride on that or just create a background thread (ew).
253
* Should be a signature at the top of the cache file.
263
255
* Paranoid mode where we never trust SHA-1 matches.
265
* Don't commit if there are no changes unless forced.
267
* --dry-run mode for commit? (Or maybe just run with
268
check-command=false?)
270
* Generally, be a bit more verbose unless --silent is specified.
272
* Function that finds all changes to files under a given directory;
273
perhaps log should use this if a directory is given.
275
* XML attributes might have trouble with filenames containing \n and
276
\r. Do we really want to support this? I think perhaps not.
278
* Remember execute bits, so that exports will work OK.
280
* Unify smart_add and plain Branch.add(); perhaps smart_add should
281
just build a list of files to add and pass that to the regular add
284
* Function to list a directory, saying in which revision each file was
285
last modified. Useful for web and gui interfaces, and slow to
286
compute one file at a time.
288
* unittest is standard, but the results are kind of ugly; would be
289
nice to make it cleaner.
291
* Check locking is correct during merge-related operations.
293
* Perhaps attempts to get locks should timeout after some period of
294
time, or at least display a progress message.
328
289
files, and respecting selective commits. Run the pre-commit check
329
290
(e.g. compile and run test suite) in there.
331
Possibly this should be done by splitting the commit function into
332
several parts (under a single interface). It is already rather
333
large. Decomposition:
335
- find tree modifications and prepare in-memory inventory
337
- export that inventory to a temporary directory
339
- run the test in that temporary directory
341
- if that succeeded, continue to actually finish the commit
343
What should be done with the text of modified files while this is
344
underway? I don't think we want to count on holding them in memory
345
and we can't trust the working files to stay in one place so I
346
suppose we need to move them into the text store, or otherwise into
347
a temporary directory.
349
If the commit does not actually complete, we would rather the
350
content was not left behind in the stores.
354
294
* GUI (maybe in Python GTK+?)
added
removed
TODO
