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?)
64
79
* ``bzr status DIR`` should give status on all files under that
67
* ``bzr log DIR`` should give changes to any files within DIR.
69
* Check all commands have decent help.
82
* ``bzr log DIR`` should give changes to any files within DIR; at the
83
moment it only lists things which modify the specific named file
84
(and not its contents)
71
86
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
87
giving options to display ids, types, etc.
79
94
temporary directory and then tar that up.)
81
96
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
83
98
* RemoteBranch could maintain a cache either in memory or on disk. We
84
99
know more than an external cache might about which files are
85
100
immutable and which can vary. On the other hand, it's much simpler
110
125
Nice for humans; less good for machine parsing.
112
127
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
128
otherwise Unix patch can't apply them. (?)
115
130
* Branch.update_revisions() inefficiently fetches revisions from the
116
131
remote server twice; once to find out what text and inventory they
117
132
need and then again to actually get the thing. This is a bit
120
135
One complicating factor here is that we don't really want to have
121
136
revisions present in the revision-store until all their constituent
124
139
The basic problem is that RemoteBranch.get_revision() and similar
125
140
methods return object, but what we really want is the raw XML, which
126
141
can be popped into our own store. That needs to be refactored.
143
* ``bzr status FOO`` where foo is ignored should say so.
145
* ``bzr mkdir A...`` should just create and add A.
147
* Guard against repeatedly merging any particular patch.
149
* More options for diff:
151
- diff two revisions of the same tree
153
- diff two different branches, optionally at different revisions
155
- diff a particular file in another tree against the corresponding
156
version in this tree (which should be the default if the second
157
parameter is a tree root)
159
- diff everything under a particular directory, in any of the above
162
- diff two files inside the same tree, even if they have different
165
- and, of course, tests for all this
167
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
169
* Reproducible performance benchmark to measure whether performance is
170
getting better or worse.
172
* ``bzr log -m foo`` should perhaps error if nothing matches?
174
* ``bzr diff -r 30 -r 40 foo.c``
168
215
At the very least we could run diffstat over the diff, or perhaps
169
216
read the status output from patch. Just knowing which files might
170
217
be modified would be enough to guide the add and commit.
172
219
Given this we might be able to import patches at 1/second or better.
174
221
* Get branch over http.
211
258
* Handle symlinks in the working directory; at the very least it
212
259
should be possible for them to be present and ignored/unknown
213
without causing assertion failures.
260
without causing assertion failures.
215
262
Eventually symlinks should be versioned.
226
273
assert it's equal.
228
275
* There are too many methods on Branch() that really manipulate the
229
WorkingTree. They should be moved across.
276
WorkingTree. They should be moved across.
231
278
Also there are some methods which are duplicated on Tree and
232
279
Inventory objects, and it should be made more clear which ones are
257
304
object interface though, but perhaps that should just be a proxy
258
305
for the elements.
260
- Less special cases for the root directory.
307
- Less special cases for the root directory.
262
309
* Perhaps inventories should remember the revision in which each file
263
310
was last changed, as well as its current state? This is a bit
270
317
* It'd be nice to pipeline multiple HTTP requests. Often we can
271
318
predict what will be wanted in future: all revisions, or all texts
272
in a particular revision, etc.
319
in a particular revision, etc.
274
321
urlgrabber's docs say they are working on batched downloads; we
275
322
could perhaps ride on that or just create a background thread (ew).
307
354
* Perhaps attempts to get locks should timeout after some period of
308
355
time, or at least display a progress message.
357
* Split out upgrade functionality from check command into a separate
360
* Don't pass around command classes but rather pass objects. This'd
361
make it cleaner to construct objects wrapping external commands.
363
* Track all merged-in revisions in a versioned add-only metafile.
365
* ``pull --clobber`` should discard any local changes not present
366
remotely. Not generally what you want, but possibly useful when
367
you're just mirroring another branch and want to keep tracking it
368
even when they e.g. uncommit or make similar non-forward movements.
369
Also for push I suppose. Clobber may not be the best name, maybe
372
* ``uncommit`` command that removes a revision from the end of the
373
revision-history; just doing this is enough to remove the commit,
374
and a new commit will automatically be made against the
375
predecessor. This can be repeated.
377
It only makes sense to delete from the tail of history, not from the
380
The revision, its inventory and texts remain floating in the store.
381
We should perhaps add the revision to a list of removed-commits, so
382
that it can be restored or at least accounted for when checking
383
consistency. This file would not be versioned, and probably should
384
not propagate when branched.
386
If we track merged revisions then we need to update this list too.
387
If the list is stored in a weave it's easy (implicit): the version
388
of the list can remain but it won't be referenced anymore. It's
389
probably best to just store this list in a weave in the first place
added
removed
TODO
