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 tht 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
20
41
* Add of a file that was present in the base revision should put back
21
42
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
23
48
* Handle diff of files which do not have a trailing newline; probably
24
49
requires patching difflib to get it exactly right, or otherwise
25
50
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
52
* Should be able to copy files between branches to preserve their
53
file-id (and perhaps eventually parentage.)
39
55
* -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.
57
* allow ``bzr st -r 300`` to show a summary of changes since then.
44
59
* ``bzr info`` should count only people with distinct email addresses as
45
60
different committers. (Or perhaps only distinct userids?)
67
82
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
71
84
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
85
giving options to display ids, types, etc.
79
92
temporary directory and then tar that up.)
81
94
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
83
96
* RemoteBranch could maintain a cache either in memory or on disk. We
84
97
know more than an external cache might about which files are
85
98
immutable and which can vary. On the other hand, it's much simpler
110
123
Nice for humans; less good for machine parsing.
112
125
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
126
otherwise Unix patch can't apply them. (?)
115
128
* Branch.update_revisions() inefficiently fetches revisions from the
116
129
remote server twice; once to find out what text and inventory they
117
130
need and then again to actually get the thing. This is a bit
120
133
One complicating factor here is that we don't really want to have
121
134
revisions present in the revision-store until all their constituent
124
137
The basic problem is that RemoteBranch.get_revision() and similar
125
138
methods return object, but what we really want is the raw XML, which
126
139
can be popped into our own store. That needs to be refactored.
141
* ``bzr status FOO`` where foo is ignored should say so.
143
* ``bzr mkdir A...`` should just create and add A.
145
* Guard against repeatedly merging any particular patch.
147
* More options for diff:
149
- diff two revisions of the same tree
151
- diff two different branches, optionally at different revisions
153
- diff a particular file in another tree against the corresponding
154
version in this tree (which should be the default if the second
155
parameter is a tree root)
157
- diff everything under a particular directory, in any of the above
160
- diff two files inside the same tree, even if they have different
163
- and, of course, tests for all this
165
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
167
* Reproducible performance benchmark to measure whether performance is
168
getting better or worse.
168
209
At the very least we could run diffstat over the diff, or perhaps
169
210
read the status output from patch. Just knowing which files might
170
211
be modified would be enough to guide the add and commit.
172
213
Given this we might be able to import patches at 1/second or better.
174
215
* Get branch over http.
211
252
* Handle symlinks in the working directory; at the very least it
212
253
should be possible for them to be present and ignored/unknown
213
without causing assertion failures.
254
without causing assertion failures.
215
256
Eventually symlinks should be versioned.
226
267
assert it's equal.
228
269
* There are too many methods on Branch() that really manipulate the
229
WorkingTree. They should be moved across.
270
WorkingTree. They should be moved across.
231
272
Also there are some methods which are duplicated on Tree and
232
273
Inventory objects, and it should be made more clear which ones are
257
298
object interface though, but perhaps that should just be a proxy
258
299
for the elements.
260
- Less special cases for the root directory.
301
- Less special cases for the root directory.
262
303
* Perhaps inventories should remember the revision in which each file
263
304
was last changed, as well as its current state? This is a bit
270
311
* It'd be nice to pipeline multiple HTTP requests. Often we can
271
312
predict what will be wanted in future: all revisions, or all texts
272
in a particular revision, etc.
313
in a particular revision, etc.
274
315
urlgrabber's docs say they are working on batched downloads; we
275
316
could perhaps ride on that or just create a background thread (ew).
307
348
* Perhaps attempts to get locks should timeout after some period of
308
349
time, or at least display a progress message.
351
* Split out upgrade functionality from check command into a separate
354
* Don't pass around command classes but rather pass objects. This'd
355
make it cleaner to construct objects wrapping external commands.
357
* Track all merged-in revisions in a versioned add-only metafile.
added
removed
TODO
