20
* is_within_any is very very dodgy
20
* ``bzr status`` should show some description of patches that are merged but
21
not yet committed. Preferably in a very compact format so that they
22
just fit on a single line; this could also be used for say ``log
25
2005-11-05 mbp Flowers for stephane
27
* Fix tests so that import errors caused by modules don't produce false reports
28
that the tests themselves don't exist.
30
* Fix tests so that one test failure doesn't prevent other tests from running
32
* print a message at the end of running the tests telling them that the
33
test log and output exists but can be removed
35
* tests for running the commit editor, and fix problem of not passing in
22
38
* Merging add of a new file clashing with an existing file doesn't
23
39
work; add gets an error that it's already versioned and the merge
68
84
* ``bzr status DIR`` should give status on all files under that
71
* ``bzr log DIR`` should give changes to any files within DIR.
87
* ``bzr log DIR`` should give changes to any files within DIR; at the
88
moment it only lists things which modify the specific named file
89
(and not its contents)
73
91
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
74
92
giving options to display ids, types, etc.
156
174
* Reproducible performance benchmark to measure whether performance is
157
175
getting better or worse.
177
* ``bzr log -m foo`` should perhaps error if nothing matches?
179
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
181
If diffing between two branches then we probably want two -r
182
options, since the revisions don't form a range that can be
183
evaluated on either one.
185
* bzr diff shouldn't diff binary files
187
* setup.py install when run from a bzr tree should freeze the tree
188
revision-id into the installed bzr.
190
* bzr script should trap ImportError and perhaps give a better error
193
* revert after a merge should possibly remove all the BASE/THIS/OTHER
194
files to get you back to where you were.
196
* files that are added and then deleted are still reported as added
198
* stores should raise KeyError, not IndexError
200
* merging from a remote branch seems to sometimes raise errors not
203
* should be possible to give a related branch when pulling from a
204
remote branch to make things faster
206
* sometimes gives "conflicting add" even when the contents are in fact
209
* BZRDIR should be in branch.py not __init__.py.
211
* ``status `` should accept a -r option to show changes relative to a revision,
163
* Merge revert patch.
165
* ``bzr mv`` that does either rename or move as in Unix.
217
* ~/.bzr.log is not written anymore for some reason.
219
* merge should add all revision and inventory XML to the local store.
221
* check should give a warning for revisions that are named in the
222
chain but not actually present in the store.
224
* remove anything outside of the branch implementation that directly
167
227
* More efficient diff of only selected files. We should be able to
168
228
just get the id for the selected files, look up their location and
202
264
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.
208
266
* revfile compression.
210
* Split inventory into per-directory files.
268
* Split inventory into per-directory files?
212
270
* Fix ignore file parsing:
328
386
* Function to list a directory, saying in which revision each file was
329
387
last modified. Useful for web and gui interfaces, and slow to
330
388
compute one file at a time.
332
* unittest is standard, but the results are kind of ugly; would be
333
nice to make it cleaner.
390
This will be done when we track file texts by referring to the
391
version that created them.
335
393
* Check locking is correct during merge-related operations.
346
404
* Track all merged-in revisions in a versioned add-only metafile.
406
* ``pull --clobber`` should discard any local changes not present
407
remotely. Not generally what you want, but possibly useful when
408
you're just mirroring another branch and want to keep tracking it
409
even when they e.g. uncommit or make similar non-forward movements.
410
Also for push I suppose. Clobber may not be the best name, maybe
413
* ``uncommit`` command that removes a revision from the end of the
414
revision-history; just doing this is enough to remove the commit,
415
and a new commit will automatically be made against the
416
predecessor. This can be repeated.
418
It only makes sense to delete from the tail of history, not from the
421
The revision, its inventory and texts remain floating in the store.
422
We should perhaps add the revision to a list of removed-commits, so
423
that it can be restored or at least accounted for when checking
424
consistency. This file would not be versioned, and probably should
425
not propagate when branched.
427
If we track merged revisions then we need to update this list too.
428
If the list is stored in a weave it's easy (implicit): the version
429
of the list can remain but it won't be referenced anymore. It's
430
probably best to just store this list in a weave in the first place
added
removed
TODO
