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
33
* Merging add of a new file clashing with an existing file doesn't
34
work; add gets an error that it's already versioned and the merge
37
* Merge should ignore the destination's working directory, otherwise
38
we get an error about the statcache when pulling from a remote
41
20
* Add of a file that was present in the base revision should put back
42
21
the previous file-id.
44
* Not sure I'm happy with needing to pass a root id to EmptyTree;
45
comparing anything against an EmptyTree with no root should have the
48
23
* Handle diff of files which do not have a trailing newline; probably
49
24
requires patching difflib to get it exactly right, or otherwise
50
25
calling out to GNU diff.
52
* Should be able to copy files between branches to preserve their
53
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
55
39
* -r option should take a revision-id as well as a revno.
57
* 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.
59
44
* ``bzr info`` should count only people with distinct email addresses as
60
45
different committers. (Or perhaps only distinct userids?)
79
64
* ``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)
67
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
86
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
87
72
giving options to display ids, types, etc.
94
79
temporary directory and then tar that up.)
96
81
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
98
83
* RemoteBranch could maintain a cache either in memory or on disk. We
99
84
know more than an external cache might about which files are
100
85
immutable and which can vary. On the other hand, it's much simpler
125
110
Nice for humans; less good for machine parsing.
127
112
* Patches should probably use only forward slashes, even on Windows,
128
otherwise Unix patch can't apply them. (?)
113
otherwise Unix patch can't apply them. (?)
130
115
* Branch.update_revisions() inefficiently fetches revisions from the
131
116
remote server twice; once to find out what text and inventory they
132
117
need and then again to actually get the thing. This is a bit
135
120
One complicating factor here is that we don't really want to have
136
121
revisions present in the revision-store until all their constituent
143
128
* ``bzr status FOO`` where foo is ignored should say so.
145
130
* ``bzr mkdir A...`` should just create and add A.
147
* Guard against repeatedly merging any particular patch.
149
* More options for diff:
151
- diff two revisions of the same tree
153
- diff two different branches, optionally at different revisions
155
- diff a particular file in another tree against the corresponding
156
version in this tree (which should be the default if the second
157
parameter is a tree root)
159
- diff everything under a particular directory, in any of the above
162
- diff two files inside the same tree, even if they have different
165
- and, of course, tests for all this
167
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
169
* Reproducible performance benchmark to measure whether performance is
170
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
137
* Merge revert patch.
139
* ``bzr mv`` that does either rename or move as in Unix.
219
141
* More efficient diff of only selected files. We should be able to
220
142
just get the id for the selected files, look up their location and
252
172
At the very least we could run diffstat over the diff, or perhaps
253
173
read the status output from patch. Just knowing which files might
254
174
be modified would be enough to guide the add and commit.
256
176
Given this we might be able to import patches at 1/second or better.
178
* Get branch over http.
180
* Pull pure updates over http.
258
182
* revfile compression.
260
* Split inventory into per-directory files?
184
* Split inventory into per-directory files.
262
186
* Fix ignore file parsing:
306
230
assert it's equal.
308
232
* There are too many methods on Branch() that really manipulate the
309
WorkingTree. They should be moved across.
233
WorkingTree. They should be moved across.
311
235
Also there are some methods which are duplicated on Tree and
312
236
Inventory objects, and it should be made more clear which ones are
337
261
object interface though, but perhaps that should just be a proxy
338
262
for the elements.
340
- Less special cases for the root directory.
264
- Less special cases for the root directory.
342
266
* Perhaps inventories should remember the revision in which each file
343
267
was last changed, as well as its current state? This is a bit
350
274
* It'd be nice to pipeline multiple HTTP requests. Often we can
351
275
predict what will be wanted in future: all revisions, or all texts
352
in a particular revision, etc.
276
in a particular revision, etc.
354
278
urlgrabber's docs say they are working on batched downloads; we
355
279
could perhaps ride on that or just create a background thread (ew).
378
302
* Function to list a directory, saying in which revision each file was
379
303
last modified. Useful for web and gui interfaces, and slow to
380
304
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.
306
* unittest is standard, but the results are kind of ugly; would be
307
nice to make it cleaner.
385
309
* Check locking is correct during merge-related operations.
390
314
* Split out upgrade functionality from check command into a separate
393
* Don't pass around command classes but rather pass objects. This'd
394
make it cleaner to construct objects wrapping external commands.
396
* 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
