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
* Fix tests so that import errors caused by modules don't produce false reports
28
that the tests themselves don't exist.
30
* print a message at the end of running the tests telling them that the
31
test log and output exists but can be removed
33
* tests for running the commit editor, and fix problem of not passing in
36
* Merging add of a new file clashing with an existing file doesn't
37
work; add gets an error that it's already versioned and the merge
40
* Merge should ignore the destination's working directory, otherwise
41
we get an error about the statcache when pulling from a remote
44
20
* Add of a file that was present in the base revision should put back
45
21
the previous file-id.
47
* Not sure I'm happy with needing to pass a root id to EmptyTree;
48
comparing anything against an EmptyTree with no root should have the
51
23
* Handle diff of files which do not have a trailing newline; probably
52
24
requires patching difflib to get it exactly right, or otherwise
53
25
calling out to GNU diff.
55
* Should be able to copy files between branches to preserve their
56
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
58
39
* -r option should take a revision-id as well as a revno.
60
* 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.
62
44
* ``bzr info`` should count only people with distinct email addresses as
63
45
different committers. (Or perhaps only distinct userids?)
97
83
temporary directory and then tar that up.)
99
85
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
101
87
* RemoteBranch could maintain a cache either in memory or on disk. We
102
88
know more than an external cache might about which files are
103
89
immutable and which can vary. On the other hand, it's much simpler
104
90
to just use an external proxy cache.
106
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
107
~/.arch-cache, containing revision information encoded almost as a
108
bunch of archives. Perhaps we could simply store full paths.
110
92
* Maybe also store directories in the statcache so that we can quickly
111
93
identify that they still exist.
113
* Diff should show timestamps; for files from the working directory we
114
can use the file itself; for files from a revision we should use the
115
commit time of the revision.
117
* Perhaps split command infrastructure from the actual command
120
* Cleaner support for negative boolean options like --no-recurse.
122
* Statcache should possibly map all file paths to / separators
124
* quotefn doubles all backslashes on Windows; this is probably not the
125
best thing to do. What would be a better way to safely represent
126
filenames? Perhaps we could doublequote things containing spaces,
127
on the principle that filenames containing quotes are unlikely?
128
Nice for humans; less good for machine parsing.
130
* Patches should probably use only forward slashes, even on Windows,
131
otherwise Unix patch can't apply them. (?)
133
* Branch.update_revisions() inefficiently fetches revisions from the
134
remote server twice; once to find out what text and inventory they
135
need and then again to actually get the thing. This is a bit
138
One complicating factor here is that we don't really want to have
139
revisions present in the revision-store until all their constituent
140
parts are also stored.
142
The basic problem is that RemoteBranch.get_revision() and similar
143
methods return object, but what we really want is the raw XML, which
144
can be popped into our own store. That needs to be refactored.
146
* ``bzr status FOO`` where foo is ignored should say so.
148
* ``bzr mkdir A...`` should just create and add A.
150
* Guard against repeatedly merging any particular patch.
152
* More options for diff:
154
- diff two revisions of the same tree
156
- diff two different branches, optionally at different revisions
158
- diff a particular file in another tree against the corresponding
159
version in this tree (which should be the default if the second
160
parameter is a tree root)
162
- diff everything under a particular directory, in any of the above
165
- diff two files inside the same tree, even if they have different
168
- and, of course, tests for all this
170
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
172
* Reproducible performance benchmark to measure whether performance is
173
getting better or worse.
175
* ``bzr log -m foo`` should perhaps error if nothing matches?
177
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
179
If diffing between two branches then we probably want two -r
180
options, since the revisions don't form a range that can be
181
evaluated on either one.
183
* bzr diff shouldn't diff binary files
185
* setup.py install when run from a bzr tree should freeze the tree
186
revision-id into the installed bzr.
188
* bzr script should trap ImportError and perhaps give a better error
191
* revert after a merge should possibly remove all the BASE/THIS/OTHER
192
files to get you back to where you were.
194
* files that are added and then deleted are still reported as added
196
* stores should raise KeyError, not IndexError
198
* merging from a remote branch seems to sometimes raise errors not
201
* should be possible to give a related branch when pulling from a
202
remote branch to make things faster
204
* sometimes gives "conflicting add" even when the contents are in fact
207
* BZRDIR should be in branch.py not __init__.py.
212
* ~/.bzr.log is not written anymore for some reason.
214
* merge should add all revision and inventory XML to the local store.
216
* check should give a warning for revisions that are named in the
217
chain but not actually present in the store.
219
* remove anything outside of the branch implementation that directly
99
* Change command functions into Command() objects, like in hct, and
100
then the grammar can be described directly in there. Since all
101
option definitions are global we can define them just once and
102
reference them from each command.
104
* Merge Aaron's merge code.
106
* Merge revert patch.
108
* ``bzr mv`` that does either rename or move as in Unix.
222
110
* More efficient diff of only selected files. We should be able to
223
111
just get the id for the selected files, look up their location and
372
265
* XML attributes might have trouble with filenames containing \n and
373
266
\r. Do we really want to support this? I think perhaps not.
375
* Remember execute bits, so that exports will work OK.
377
* Unify smart_add and plain Branch.add(); perhaps smart_add should
378
just build a list of files to add and pass that to the regular add
381
* Function to list a directory, saying in which revision each file was
382
last modified. Useful for web and gui interfaces, and slow to
383
compute one file at a time.
385
This will be done when we track file texts by referring to the
386
version that created them.
388
* Check locking is correct during merge-related operations.
390
* Perhaps attempts to get locks should timeout after some period of
391
time, or at least display a progress message.
393
* Split out upgrade functionality from check command into a separate
396
* Don't pass around command classes but rather pass objects. This'd
397
make it cleaner to construct objects wrapping external commands.
399
* Track all merged-in revisions in a versioned add-only metafile.
401
* ``pull --clobber`` should discard any local changes not present
402
remotely. Not generally what you want, but possibly useful when
403
you're just mirroring another branch and want to keep tracking it
404
even when they e.g. uncommit or make similar non-forward movements.
405
Also for push I suppose. Clobber may not be the best name, maybe
408
* ``uncommit`` command that removes a revision from the end of the
409
revision-history; just doing this is enough to remove the commit,
410
and a new commit will automatically be made against the
411
predecessor. This can be repeated.
413
It only makes sense to delete from the tail of history, not from the
416
The revision, its inventory and texts remain floating in the store.
417
We should perhaps add the revision to a list of removed-commits, so
418
that it can be restored or at least accounted for when checking
419
consistency. This file would not be versioned, and probably should
420
not propagate when branched.
422
If we track merged revisions then we need to update this list too.
423
If the list is stored in a weave it's easy (implicit): the version
424
of the list can remain but it won't be referenced anymore. It's
425
probably best to just store this list in a weave in the first place
added
removed
TODO
