20
* Fix tests so that import errors caused by modules don't produce false reports
21
that the tests themselves don't exist.
23
* Fix tests so that one test failure doesn't prevent other tests from running
25
* print a message at the end of running the tests telling them that the
26
test log and output exists but can be removed
28
* tests for running the commit editor, and fix problem of not passing in
20
* is_within_any is very very dodgy
31
22
* Merging add of a new file clashing with an existing file doesn't
32
23
work; add gets an error that it's already versioned and the merge
53
44
* -r option should take a revision-id as well as a revno.
46
* allow ``bzr st -r 300`` to show a summary of changes since then.
55
48
* ``bzr info`` should count only people with distinct email addresses as
56
49
different committers. (Or perhaps only distinct userids?)
75
68
* ``bzr status DIR`` should give status on all files under that
78
* ``bzr log DIR`` should give changes to any files within DIR; at the
79
moment it only lists things which modify the specific named file
80
(and not its contents)
71
* ``bzr log DIR`` should give changes to any files within DIR.
82
73
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
83
74
giving options to display ids, types, etc.
76
* Split BzrError into various more specific subclasses for different
77
errors people might want to catch.
79
* If the export destination ends in '.tar', '.tar.gz', etc then create
80
a tarball instead of a directory. (Need to actually make a
81
temporary directory and then tar that up.)
83
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
85
85
* RemoteBranch could maintain a cache either in memory or on disk. We
86
86
know more than an external cache might about which files are
87
87
immutable and which can vary. On the other hand, it's much simpler
127
127
methods return object, but what we really want is the raw XML, which
128
128
can be popped into our own store. That needs to be refactored.
130
* ``bzr status FOO`` where foo is ignored should say so.
132
* ``bzr mkdir A...`` should just create and add A.
130
134
* Guard against repeatedly merging any particular patch.
132
136
* More options for diff:
148
152
- and, of course, tests for all this
154
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
150
156
* Reproducible performance benchmark to measure whether performance is
151
157
getting better or worse.
153
* ``bzr log -m foo`` should perhaps error if nothing matches?
155
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
157
If diffing between two branches then we probably want two -r
158
options, since the revisions don't form a range that can be
159
evaluated on either one.
161
* bzr diff shouldn't diff binary files
163
* setup.py install when run from a bzr tree should freeze the tree
164
revision-id into the installed bzr.
166
* bzr script should trap ImportError and perhaps give a better error
169
* revert after a merge should possibly remove all the BASE/THIS/OTHER
170
files to get you back to where you were.
172
* files that are added and then deleted are still reported as added
174
* stores should raise KeyError, not IndexError
176
* merging from a remote branch seems to sometimes raise errors not
179
* should be possible to give a related branch when pulling from a
180
remote branch to make things faster
182
* sometimes gives "conflicting add" even when the contents are in fact
185
* BZRDIR should be in branch.py not __init__.py.
190
* merge should add all revision and inventory XML to the local store.
192
* check should give a warning for revisions that are named in the
193
chain but not actually present in the store.
195
* remove anything outside of the branch implementation that directly
163
* Merge revert patch.
165
* ``bzr mv`` that does either rename or move as in Unix.
198
167
* More efficient diff of only selected files. We should be able to
199
168
just get the id for the selected files, look up their location and
200
169
diff just those files. No need to traverse the entire inventories.
171
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
172
under that directory.
202
174
* Fix up Inventory objects to represent root object as an entry.
204
176
* Don't convert entire entry from ElementTree to an object when it is
232
202
Given this we might be able to import patches at 1/second or better.
204
* Get branch over http.
206
* Pull pure updates over http.
234
208
* revfile compression.
236
* Split inventory into per-directory files?
210
* Split inventory into per-directory files.
238
212
* Fix ignore file parsing:
281
255
- Class that describes the state of a working tree so we can just
282
256
assert it's equal.
258
* There are too many methods on Branch() that really manipulate the
259
WorkingTree. They should be moved across.
261
Also there are some methods which are duplicated on Tree and
262
Inventory objects, and it should be made more clear which ones are
263
proxies and which ones behave differently, and how.
284
265
* Try using XSLT to add some formatting to REST-generated HTML. Or
285
266
maybe write a small Python program that specifies a header and foot
286
267
for the pages and calls into the docutils libraries.
303
284
- Hold the ElementTree in memory in the Inventory object and work
304
285
directly on that, rather than converting into Python objects every
305
time it is read in. Probably still expose it through some kind of
286
time it is read in. Probably still exposoe it through some kind of
306
287
object interface though, but perhaps that should just be a proxy
307
288
for the elements.
315
296
* stat cache should perhaps only stat files as necessary, rather than
316
297
doing them all up-front. On the other hand, that disallows the
317
optimization of stating them in inode order.
298
opimization of stating them in inode order.
319
300
* It'd be nice to pipeline multiple HTTP requests. Often we can
320
301
predict what will be wanted in future: all revisions, or all texts
336
319
* XML attributes might have trouble with filenames containing \n and
337
320
\r. Do we really want to support this? I think perhaps not.
322
* Remember execute bits, so that exports will work OK.
339
324
* Unify smart_add and plain Branch.add(); perhaps smart_add should
340
325
just build a list of files to add and pass that to the regular add
343
328
* Function to list a directory, saying in which revision each file was
344
last modified. Useful for web and GUI interfaces, and slow to
329
last modified. Useful for web and gui interfaces, and slow to
345
330
compute one file at a time.
347
This will be done when we track file texts by referring to the
348
version that created them.
332
* unittest is standard, but the results are kind of ugly; would be
333
nice to make it cleaner.
350
335
* Check locking is correct during merge-related operations.
352
337
* Perhaps attempts to get locks should timeout after some period of
353
338
time, or at least display a progress message.
340
* Split out upgrade functionality from check command into a separate
355
343
* Don't pass around command classes but rather pass objects. This'd
356
344
make it cleaner to construct objects wrapping external commands.
358
346
* Track all merged-in revisions in a versioned add-only metafile.
360
* ``uncommit`` command that removes a revision from the end of the
361
revision-history; just doing this is enough to remove the commit,
362
and a new commit will automatically be made against the
363
predecessor. This can be repeated.
365
It only makes sense to delete from the tail of history.
367
This has been implemented, but it does not remove the texts from
added
removed
TODO
