20
* Merging add of a new file clashing with an existing file doesn't
21
work; add gets an error that it's already versioned and the merge
24
* Merge should ignore the destination's working directory, otherwise
25
we get an error about the statcache when pulling from a remote
28
20
* Add of a file that was present in the base revision should put back
29
21
the previous file-id.
31
* Not sure I'm happy with needing to pass a root id to EmptyTree;
32
comparing anything against an EmptyTree with no root should have the
35
23
* Handle diff of files which do not have a trailing newline; probably
36
24
requires patching difflib to get it exactly right, or otherwise
37
25
calling out to GNU diff.
39
* Should be able to copy files between branches to preserve their
40
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
42
39
* -r option should take a revision-id as well as a revno.
44
* 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.
46
44
* ``bzr info`` should count only people with distinct email addresses as
47
45
different committers. (Or perhaps only distinct userids?)
69
67
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
71
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
72
giving options to display ids, types, etc.
79
79
temporary directory and then tar that up.)
81
81
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
83
83
* RemoteBranch could maintain a cache either in memory or on disk. We
84
84
know more than an external cache might about which files are
85
85
immutable and which can vary. On the other hand, it's much simpler
110
110
Nice for humans; less good for machine parsing.
112
112
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
113
otherwise Unix patch can't apply them. (?)
115
115
* Branch.update_revisions() inefficiently fetches revisions from the
116
116
remote server twice; once to find out what text and inventory they
117
117
need and then again to actually get the thing. This is a bit
120
120
One complicating factor here is that we don't really want to have
121
121
revisions present in the revision-store until all their constituent
124
124
The basic problem is that RemoteBranch.get_revision() and similar
125
125
methods return object, but what we really want is the raw XML, which
126
126
can be popped into our own store. That needs to be refactored.
128
* ``bzr status FOO`` where foo is ignored should say so.
130
* ``bzr mkdir A...`` should just create and add A.
132
* Guard against repeatedly merging any particular patch.
134
* More options for diff:
136
- diff two revisions of the same tree
138
- diff two different branches, optionally at different revisions
140
- diff a particular file in another tree against the corresponding
141
version in this tree (which should be the default if the second
142
parameter is a tree root)
144
- diff everything under a particular directory, in any of the above
147
- diff two files inside the same tree, even if they have different
150
- and, of course, tests for all this
152
* stat-cache update is too slow for some reason - why is Python making
153
a lot of futex calls?
155
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
197
168
At the very least we could run diffstat over the diff, or perhaps
198
169
read the status output from patch. Just knowing which files might
199
170
be modified would be enough to guide the add and commit.
201
172
Given this we might be able to import patches at 1/second or better.
203
174
* Get branch over http.
240
211
* Handle symlinks in the working directory; at the very least it
241
212
should be possible for them to be present and ignored/unknown
242
without causing assertion failures.
213
without causing assertion failures.
244
215
Eventually symlinks should be versioned.
255
226
assert it's equal.
257
228
* There are too many methods on Branch() that really manipulate the
258
WorkingTree. They should be moved across.
229
WorkingTree. They should be moved across.
260
231
Also there are some methods which are duplicated on Tree and
261
232
Inventory objects, and it should be made more clear which ones are
286
257
object interface though, but perhaps that should just be a proxy
287
258
for the elements.
289
- Less special cases for the root directory.
260
- Less special cases for the root directory.
291
262
* Perhaps inventories should remember the revision in which each file
292
263
was last changed, as well as its current state? This is a bit
299
270
* It'd be nice to pipeline multiple HTTP requests. Often we can
300
271
predict what will be wanted in future: all revisions, or all texts
301
in a particular revision, etc.
272
in a particular revision, etc.
303
274
urlgrabber's docs say they are working on batched downloads; we
304
275
could perhaps ride on that or just create a background thread (ew).
336
307
* Perhaps attempts to get locks should timeout after some period of
337
308
time, or at least display a progress message.
339
* Split out upgrade functionality from check command into a separate
342
* Don't pass around command classes but rather pass objects. This'd
343
make it cleaner to construct objects wrapping external commands.
345
* Track all merged-in revisions in a versioned add-only metafile.
added
removed
TODO
