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
31
* Merging add of a new file clashing with an existing file doesn't
21
32
work; add gets an error that it's already versioned and the merge
66
75
* ``bzr status DIR`` should give status on all files under that
69
* ``bzr log DIR`` should give changes to any files within DIR.
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
82
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
83
giving options to display ids, types, etc.
74
* Split BzrError into various more specific subclasses for different
75
errors people might want to catch.
77
* If the export destination ends in '.tar', '.tar.gz', etc then create
78
a tarball instead of a directory. (Need to actually make a
79
temporary directory and then tar that up.)
81
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
83
85
* RemoteBranch could maintain a cache either in memory or on disk. We
84
86
know more than an external cache might about which files are
85
87
immutable and which can vary. On the other hand, it's much simpler
125
127
methods return object, but what we really want is the raw XML, which
126
128
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.
132
130
* Guard against repeatedly merging any particular patch.
134
132
* More options for diff:
150
148
- and, of course, tests for all this
152
* stat-cache update is too slow for some reason - why is Python making
153
a lot of futex calls?
155
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
150
* Reproducible performance benchmark to measure whether performance is
151
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.
162
* Merge revert patch.
164
* ``bzr mv`` that does either rename or move as in Unix.
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
166
198
* More efficient diff of only selected files. We should be able to
167
199
just get the id for the selected files, look up their location and
168
200
diff just those files. No need to traverse the entire inventories.
170
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
171
under that directory.
173
202
* Fix up Inventory objects to represent root object as an entry.
175
204
* Don't convert entire entry from ElementTree to an object when it is
201
232
Given this we might be able to import patches at 1/second or better.
203
* Get branch over http.
205
* Pull pure updates over http.
207
234
* revfile compression.
209
* Split inventory into per-directory files.
236
* Split inventory into per-directory files?
211
238
* Fix ignore file parsing:
254
281
- Class that describes the state of a working tree so we can just
255
282
assert it's equal.
257
* There are too many methods on Branch() that really manipulate the
258
WorkingTree. They should be moved across.
260
Also there are some methods which are duplicated on Tree and
261
Inventory objects, and it should be made more clear which ones are
262
proxies and which ones behave differently, and how.
264
284
* Try using XSLT to add some formatting to REST-generated HTML. Or
265
285
maybe write a small Python program that specifies a header and foot
266
286
for the pages and calls into the docutils libraries.
283
303
- Hold the ElementTree in memory in the Inventory object and work
284
304
directly on that, rather than converting into Python objects every
285
time it is read in. Probably still exposoe it through some kind of
305
time it is read in. Probably still expose it through some kind of
286
306
object interface though, but perhaps that should just be a proxy
287
307
for the elements.
295
315
* stat cache should perhaps only stat files as necessary, rather than
296
316
doing them all up-front. On the other hand, that disallows the
297
opimization of stating them in inode order.
317
optimization of stating them in inode order.
299
319
* It'd be nice to pipeline multiple HTTP requests. Often we can
300
320
predict what will be wanted in future: all revisions, or all texts
318
336
* XML attributes might have trouble with filenames containing \n and
319
337
\r. Do we really want to support this? I think perhaps not.
321
* Remember execute bits, so that exports will work OK.
323
339
* Unify smart_add and plain Branch.add(); perhaps smart_add should
324
340
just build a list of files to add and pass that to the regular add
327
343
* Function to list a directory, saying in which revision each file was
328
last modified. Useful for web and gui interfaces, and slow to
344
last modified. Useful for web and GUI interfaces, and slow to
329
345
compute one file at a time.
331
* unittest is standard, but the results are kind of ugly; would be
332
nice to make it cleaner.
347
This will be done when we track file texts by referring to the
348
version that created them.
334
350
* Check locking is correct during merge-related operations.
336
352
* Perhaps attempts to get locks should timeout after some period of
337
353
time, or at least display a progress message.
339
* Split out upgrade functionality from check command into a separate
342
355
* Don't pass around command classes but rather pass objects. This'd
343
356
make it cleaner to construct objects wrapping external commands.
345
358
* 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, not from the
368
The revision, its inventory and texts remain floating in the store.
369
We should perhaps add the revision to a list of removed-commits, so
370
that it can be restored or at least accounted for when checking
371
consistency. This file would not be versioned, and probably should
372
not propagate when branched.
374
If we track merged revisions then we need to update this list too.
375
If the list is stored in a weave it's easy (implicit): the version
376
of the list can remain but it won't be referenced anymore. It's
377
probably best to just store this list in a weave in the first place
added
removed
TODO
