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
20
46
* Add of a file that was present in the base revision should put back
21
47
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
23
53
* Handle diff of files which do not have a trailing newline; probably
24
54
requires patching difflib to get it exactly right, or otherwise
25
55
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
60
* -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.
29
64
* ``bzr info`` should count only people with distinct email addresses as
30
65
different committers. (Or perhaps only distinct userids?)
49
84
* ``bzr status DIR`` should give status on all files under that
52
* ``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)
54
91
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
55
92
giving options to display ids, types, etc.
62
99
temporary directory and then tar that up.)
64
101
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
66
103
* RemoteBranch could maintain a cache either in memory or on disk. We
67
104
know more than an external cache might about which files are
68
105
immutable and which can vary. On the other hand, it's much simpler
93
130
Nice for humans; less good for machine parsing.
95
132
* Patches should probably use only forward slashes, even on Windows,
96
otherwise Unix patch can't apply them. (?)
133
otherwise Unix patch can't apply them. (?)
98
135
* Branch.update_revisions() inefficiently fetches revisions from the
99
136
remote server twice; once to find out what text and inventory they
100
137
need and then again to actually get the thing. This is a bit
103
140
One complicating factor here is that we don't really want to have
104
141
revisions present in the revision-store until all their constituent
113
150
* ``bzr mkdir A...`` should just create and add A.
115
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
* Reproducible performance benchmark to measure whether performance is
173
getting better or worse.
175
* ``bzr log -m foo`` should perhaps error if nothing matches?
177
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
179
If diffing between two branches then we probably want two -r
180
options, since the revisions don't form a range that can be
181
evaluated on either one.
183
* bzr diff shouldn't diff binary files
185
* setup.py install when run from a bzr tree should freeze the tree
186
revision-id into the installed bzr.
188
* bzr script should trap ImportError and perhaps give a better error
191
* revert after a merge should possibly remove all the BASE/THIS/OTHER
192
files to get you back to where you were.
194
* files that are added and then deleted are still reported as added
196
* stores should raise KeyError, not IndexError
198
* merging from a remote branch seems to sometimes raise errors not
201
* should be possible to give a related branch when pulling from a
202
remote branch to make things faster
204
* sometimes gives "conflicting add" even when the contents are in fact
207
* BZRDIR should be in branch.py not __init__.py.
209
* ``status `` should accept a -r option to show changes relative to a revision,
122
* Merge revert patch.
124
* ``bzr mv`` that does either rename or move as in Unix.
215
* ~/.bzr.log is not written anymore for some reason.
217
* merge should add all revision and inventory XML to the local store.
219
* check should give a warning for revisions that are named in the
220
chain but not actually present in the store.
222
* remove anything outside of the branch implementation that directly
126
225
* More efficient diff of only selected files. We should be able to
127
226
just get the id for the selected files, look up their location and
157
258
At the very least we could run diffstat over the diff, or perhaps
158
259
read the status output from patch. Just knowing which files might
159
260
be modified would be enough to guide the add and commit.
161
262
Given this we might be able to import patches at 1/second or better.
163
* Get branch over http.
165
* Pull pure updates over http.
167
264
* revfile compression.
169
* Split inventory into per-directory files.
266
* Split inventory into per-directory files?
171
268
* Fix ignore file parsing:
215
312
assert it's equal.
217
314
* There are too many methods on Branch() that really manipulate the
218
WorkingTree. They should be moved across.
315
WorkingTree. They should be moved across.
220
317
Also there are some methods which are duplicated on Tree and
221
318
Inventory objects, and it should be made more clear which ones are
246
343
object interface though, but perhaps that should just be a proxy
247
344
for the elements.
249
- Less special cases for the root directory.
346
- Less special cases for the root directory.
251
348
* Perhaps inventories should remember the revision in which each file
252
349
was last changed, as well as its current state? This is a bit
259
356
* It'd be nice to pipeline multiple HTTP requests. Often we can
260
357
predict what will be wanted in future: all revisions, or all texts
261
in a particular revision, etc.
358
in a particular revision, etc.
263
360
urlgrabber's docs say they are working on batched downloads; we
264
361
could perhaps ride on that or just create a background thread (ew).
287
384
* Function to list a directory, saying in which revision each file was
288
385
last modified. Useful for web and gui interfaces, and slow to
289
386
compute one file at a time.
291
* unittest is standard, but the results are kind of ugly; would be
292
nice to make it cleaner.
388
This will be done when we track file texts by referring to the
389
version that created them.
294
391
* Check locking is correct during merge-related operations.
305
402
* Track all merged-in revisions in a versioned add-only metafile.
404
* ``pull --clobber`` should discard any local changes not present
405
remotely. Not generally what you want, but possibly useful when
406
you're just mirroring another branch and want to keep tracking it
407
even when they e.g. uncommit or make similar non-forward movements.
408
Also for push I suppose. Clobber may not be the best name, maybe
411
* ``uncommit`` command that removes a revision from the end of the
412
revision-history; just doing this is enough to remove the commit,
413
and a new commit will automatically be made against the
414
predecessor. This can be repeated.
416
It only makes sense to delete from the tail of history, not from the
419
The revision, its inventory and texts remain floating in the store.
420
We should perhaps add the revision to a list of removed-commits, so
421
that it can be restored or at least accounted for when checking
422
consistency. This file would not be versioned, and probably should
423
not propagate when branched.
425
If we track merged revisions then we need to update this list too.
426
If the list is stored in a weave it's easy (implicit): the version
427
of the list can remain but it won't be referenced anymore. It's
428
probably best to just store this list in a weave in the first place
added
removed
TODO
