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
* print a message at the end of running the tests telling them that the
28
test log and output exists but can be removed
30
* tests for running the commit editor, and fix problem of not passing in
20
* is_within_any is very very dodgy
33
22
* Merging add of a new file clashing with an existing file doesn't
34
23
work; add gets an error that it's already versioned and the merge
79
68
* ``bzr status DIR`` should give status on all files under that
82
* ``bzr log DIR`` should give changes to any files within DIR; at the
83
moment it only lists things which modify the specific named file
84
(and not its contents)
71
* ``bzr log DIR`` should give changes to any files within DIR.
86
73
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
87
74
giving options to display ids, types, etc.
169
156
* Reproducible performance benchmark to measure whether performance is
170
157
getting better or worse.
172
* ``bzr log -m foo`` should perhaps error if nothing matches?
174
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
176
If diffing between two branches then we probably want two -r
177
options, since the revisions don't form a range that can be
178
evaluated on either one.
180
* bzr diff shouldn't diff binary files
182
* setup.py install when run from a bzr tree should freeze the tree
183
revision-id into the installed bzr.
185
* bzr script should trap ImportError and perhaps give a better error
188
* revert after a merge should possibly remove all the BASE/THIS/OTHER
189
files to get you back to where you were.
191
* files that are added and then deleted are still reported as added
193
* stores should raise KeyError, not IndexError
195
* merging from a remote branch seems to sometimes raise errors not
198
* should be possible to give a related branch when pulling from a
199
remote branch to make things faster
201
* sometimes gives "conflicting add" even when the contents are in fact
204
* BZRDIR should be in branch.py not __init__.py.
209
* ~/.bzr.log is not written anymore for some reason.
211
* merge should add all revision and inventory XML to the local store.
213
* check should give a warning for revisions that are named in the
214
chain but not actually present in the store.
216
* 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.
219
167
* More efficient diff of only selected files. We should be able to
220
168
just get the id for the selected files, look up their location and
256
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.
258
208
* revfile compression.
260
* Split inventory into per-directory files?
210
* Split inventory into per-directory files.
262
212
* Fix ignore file parsing:
378
328
* Function to list a directory, saying in which revision each file was
379
329
last modified. Useful for web and gui interfaces, and slow to
380
330
compute one file at a time.
382
This will be done when we track file texts by referring to the
383
version that created them.
332
* unittest is standard, but the results are kind of ugly; would be
333
nice to make it cleaner.
385
335
* Check locking is correct during merge-related operations.
396
346
* Track all merged-in revisions in a versioned add-only metafile.
398
* ``pull --clobber`` should discard any local changes not present
399
remotely. Not generally what you want, but possibly useful when
400
you're just mirroring another branch and want to keep tracking it
401
even when they e.g. uncommit or make similar non-forward movements.
402
Also for push I suppose. Clobber may not be the best name, maybe
405
* ``uncommit`` command that removes a revision from the end of the
406
revision-history; just doing this is enough to remove the commit,
407
and a new commit will automatically be made against the
408
predecessor. This can be repeated.
410
It only makes sense to delete from the tail of history, not from the
413
The revision, its inventory and texts remain floating in the store.
414
We should perhaps add the revision to a list of removed-commits, so
415
that it can be restored or at least accounted for when checking
416
consistency. This file would not be versioned, and probably should
417
not propagate when branched.
419
If we track merged revisions then we need to update this list too.
420
If the list is stored in a weave it's easy (implicit): the version
421
of the list can remain but it won't be referenced anymore. It's
422
probably best to just store this list in a weave in the first place
added
removed
TODO
