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
20
30
* Add of a file that was present in the base revision should put back
21
31
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
23
37
* Handle diff of files which do not have a trailing newline; probably
24
38
requires patching difflib to get it exactly right, or otherwise
25
39
calling out to GNU diff.
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
41
* Should be able to copy files between branches to preserve their
42
file-id (and perhaps eventually parentage.)
39
44
* -r option should take a revision-id as well as a revno.
41
* ``bzr info`` could show space used by working tree, versioned files,
42
unknown and ignored files.
46
* allow ``bzr st -r 300`` to show a summary of changes since then.
44
48
* ``bzr info`` should count only people with distinct email addresses as
45
49
different committers. (Or perhaps only distinct userids?)
67
71
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
71
73
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
74
giving options to display ids, types, etc.
79
81
temporary directory and then tar that up.)
81
83
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
83
85
* RemoteBranch could maintain a cache either in memory or on disk. We
84
86
know more than an external cache might about which files are
85
87
immutable and which can vary. On the other hand, it's much simpler
110
112
Nice for humans; less good for machine parsing.
112
114
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
115
otherwise Unix patch can't apply them. (?)
115
117
* Branch.update_revisions() inefficiently fetches revisions from the
116
118
remote server twice; once to find out what text and inventory they
117
119
need and then again to actually get the thing. This is a bit
120
122
One complicating factor here is that we don't really want to have
121
123
revisions present in the revision-store until all their constituent
128
130
* ``bzr status FOO`` where foo is ignored should say so.
130
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.
172
198
At the very least we could run diffstat over the diff, or perhaps
173
199
read the status output from patch. Just knowing which files might
174
200
be modified would be enough to guide the add and commit.
176
202
Given this we might be able to import patches at 1/second or better.
178
204
* Get branch over http.
215
241
* Handle symlinks in the working directory; at the very least it
216
242
should be possible for them to be present and ignored/unknown
217
without causing assertion failures.
243
without causing assertion failures.
219
245
Eventually symlinks should be versioned.
230
256
assert it's equal.
232
258
* There are too many methods on Branch() that really manipulate the
233
WorkingTree. They should be moved across.
259
WorkingTree. They should be moved across.
235
261
Also there are some methods which are duplicated on Tree and
236
262
Inventory objects, and it should be made more clear which ones are
261
287
object interface though, but perhaps that should just be a proxy
262
288
for the elements.
264
- Less special cases for the root directory.
290
- Less special cases for the root directory.
266
292
* Perhaps inventories should remember the revision in which each file
267
293
was last changed, as well as its current state? This is a bit
274
300
* It'd be nice to pipeline multiple HTTP requests. Often we can
275
301
predict what will be wanted in future: all revisions, or all texts
276
in a particular revision, etc.
302
in a particular revision, etc.
278
304
urlgrabber's docs say they are working on batched downloads; we
279
305
could perhaps ride on that or just create a background thread (ew).
added
removed
TODO
