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
38
* Merging add of a new file clashing with an existing file doesn't
39
work; add gets an error that it's already versioned and the merge
42
* Merge should ignore the destination's working directory, otherwise
43
we get an error about the statcache when pulling from a remote
46
20
* Add of a file that was present in the base revision should put back
47
21
the previous file-id.
49
* Not sure I'm happy with needing to pass a root id to EmptyTree;
50
comparing anything against an EmptyTree with no root should have the
53
23
* Handle diff of files which do not have a trailing newline; probably
54
24
requires patching difflib to get it exactly right, or otherwise
55
25
calling out to GNU diff.
57
* Should be able to copy files between branches to preserve their
58
file-id (and perhaps eventually parentage.)
27
* Import ElementTree update patch.
29
* Plugins that provide commands. By just installing a file into some
30
directory (e.g. ``/usr/share/bzr/plugins``) it should be possible to
31
create new top-level commands (``bzr frob``). Extensions can be
32
written in either Python (in which case they use the bzrlib API) or
33
in a separate process (in sh, C, whatever). It should be possible
34
to get help for plugin commands.
36
* Smart rewrap text in help messages to fit in $COLUMNS (or equivalent
60
39
* -r option should take a revision-id as well as a revno.
62
* allow ``bzr st -r 300`` to show a summary of changes since then.
41
* ``bzr info`` could show space used by working tree, versioned files,
42
unknown and ignored files.
64
44
* ``bzr info`` should count only people with distinct email addresses as
65
45
different committers. (Or perhaps only distinct userids?)
84
64
* ``bzr status DIR`` should give status on all files under that
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)
67
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
91
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
92
72
giving options to display ids, types, etc.
130
110
Nice for humans; less good for machine parsing.
132
112
* Patches should probably use only forward slashes, even on Windows,
133
otherwise Unix patch can't apply them. (?)
113
otherwise Unix patch can't apply them. (?)
135
115
* Branch.update_revisions() inefficiently fetches revisions from the
136
116
remote server twice; once to find out what text and inventory they
137
117
need and then again to actually get the thing. This is a bit
140
120
One complicating factor here is that we don't really want to have
141
121
revisions present in the revision-store until all their constituent
144
124
The basic problem is that RemoteBranch.get_revision() and similar
145
125
methods return object, but what we really want is the raw XML, which
146
126
can be popped into our own store. That needs to be refactored.
148
* ``bzr status FOO`` where foo is ignored should say so.
150
* ``bzr mkdir A...`` should just create and add A.
152
* Guard against repeatedly merging any particular patch.
154
* More options for diff:
156
- diff two revisions of the same tree
158
- diff two different branches, optionally at different revisions
160
- diff a particular file in another tree against the corresponding
161
version in this tree (which should be the default if the second
162
parameter is a tree root)
164
- diff everything under a particular directory, in any of the above
167
- diff two files inside the same tree, even if they have different
170
- and, of course, tests for all this
172
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
174
* Reproducible performance benchmark to measure whether performance is
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,
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
133
* Merge revert patch.
135
* ``bzr mv`` that does either rename or move as in Unix.
227
137
* More efficient diff of only selected files. We should be able to
228
138
just get the id for the selected files, look up their location and
260
168
At the very least we could run diffstat over the diff, or perhaps
261
169
read the status output from patch. Just knowing which files might
262
170
be modified would be enough to guide the add and commit.
264
172
Given this we might be able to import patches at 1/second or better.
174
* Get branch over http.
176
* Pull pure updates over http.
266
178
* revfile compression.
268
* Split inventory into per-directory files?
180
* Split inventory into per-directory files.
270
182
* Fix ignore file parsing:
358
270
* It'd be nice to pipeline multiple HTTP requests. Often we can
359
271
predict what will be wanted in future: all revisions, or all texts
360
in a particular revision, etc.
272
in a particular revision, etc.
362
274
urlgrabber's docs say they are working on batched downloads; we
363
275
could perhaps ride on that or just create a background thread (ew).
386
298
* Function to list a directory, saying in which revision each file was
387
299
last modified. Useful for web and gui interfaces, and slow to
388
300
compute one file at a time.
390
This will be done when we track file texts by referring to the
391
version that created them.
302
* unittest is standard, but the results are kind of ugly; would be
303
nice to make it cleaner.
393
305
* Check locking is correct during merge-related operations.
395
307
* Perhaps attempts to get locks should timeout after some period of
396
308
time, or at least display a progress message.
398
* Split out upgrade functionality from check command into a separate
401
* Don't pass around command classes but rather pass objects. This'd
402
make it cleaner to construct objects wrapping external commands.
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
