20
* is_within_any is very very dodgy
22
* Merging add of a new file clashing with an existing file doesn't
23
work; add gets an error that it's already versioned and the merge
26
* Merge should ignore the destination's working directory, otherwise
27
we get an error about the statcache when pulling from a remote
30
20
* Add of a file that was present in the base revision should put back
31
21
the previous file-id.
33
* Not sure I'm happy with needing to pass a root id to EmptyTree;
34
comparing anything against an EmptyTree with no root should have the
37
23
* Handle diff of files which do not have a trailing newline; probably
38
24
requires patching difflib to get it exactly right, or otherwise
39
25
calling out to GNU diff.
41
* Should be able to copy files between branches to preserve their
42
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
44
39
* -r option should take a revision-id as well as a revno.
46
* 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.
48
44
* ``bzr info`` should count only people with distinct email addresses as
49
45
different committers. (Or perhaps only distinct userids?)
71
67
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
73
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
74
72
giving options to display ids, types, etc.
81
79
temporary directory and then tar that up.)
83
81
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
85
83
* RemoteBranch could maintain a cache either in memory or on disk. We
86
84
know more than an external cache might about which files are
87
85
immutable and which can vary. On the other hand, it's much simpler
112
110
Nice for humans; less good for machine parsing.
114
112
* Patches should probably use only forward slashes, even on Windows,
115
otherwise Unix patch can't apply them. (?)
117
* Branch.update_revisions() inefficiently fetches revisions from the
118
remote server twice; once to find out what text and inventory they
119
need and then again to actually get the thing. This is a bit
122
One complicating factor here is that we don't really want to have
123
revisions present in the revision-store until all their constituent
124
parts are also stored.
126
The basic problem is that RemoteBranch.get_revision() and similar
127
methods return object, but what we really want is the raw XML, which
128
can be popped into our own store. That needs to be refactored.
130
* ``bzr status FOO`` where foo is ignored should say so.
132
* ``bzr mkdir A...`` should just create and add A.
134
* Guard against repeatedly merging any particular patch.
136
* More options for diff:
138
- diff two revisions of the same tree
140
- diff two different branches, optionally at different revisions
142
- diff a particular file in another tree against the corresponding
143
version in this tree (which should be the default if the second
144
parameter is a tree root)
146
- diff everything under a particular directory, in any of the above
149
- diff two files inside the same tree, even if they have different
152
- and, of course, tests for all this
154
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
156
* Reproducible performance benchmark to measure whether performance is
157
getting better or worse.
113
otherwise Unix patch can't apply them. (?)
198
154
At the very least we could run diffstat over the diff, or perhaps
199
155
read the status output from patch. Just knowing which files might
200
156
be modified would be enough to guide the add and commit.
202
158
Given this we might be able to import patches at 1/second or better.
204
160
* Get branch over http.
241
197
* Handle symlinks in the working directory; at the very least it
242
198
should be possible for them to be present and ignored/unknown
243
without causing assertion failures.
199
without causing assertion failures.
245
201
Eventually symlinks should be versioned.
256
212
assert it's equal.
258
214
* There are too many methods on Branch() that really manipulate the
259
WorkingTree. They should be moved across.
215
WorkingTree. They should be moved across.
261
217
Also there are some methods which are duplicated on Tree and
262
218
Inventory objects, and it should be made more clear which ones are
287
243
object interface though, but perhaps that should just be a proxy
288
244
for the elements.
290
- Less special cases for the root directory.
246
- Less special cases for the root directory.
292
248
* Perhaps inventories should remember the revision in which each file
293
249
was last changed, as well as its current state? This is a bit
300
256
* It'd be nice to pipeline multiple HTTP requests. Often we can
301
257
predict what will be wanted in future: all revisions, or all texts
302
in a particular revision, etc.
258
in a particular revision, etc.
304
260
urlgrabber's docs say they are working on batched downloads; we
305
261
could perhaps ride on that or just create a background thread (ew).
337
293
* Perhaps attempts to get locks should timeout after some period of
338
294
time, or at least display a progress message.
340
* Split out upgrade functionality from check command into a separate
343
* Don't pass around command classes but rather pass objects. This'd
344
make it cleaner to construct objects wrapping external commands.
346
* Track all merged-in revisions in a versioned add-only metafile.
added
removed
TODO
