20
* Fix tests so that import errors caused by modules don't produce false reports
21
that the tests themselves don't exist.
23
* Fix tests so that one test failure doesn't prevent other tests from running
25
* print a message at the end of running the tests telling them that the
26
test log and output exists but can be removed
28
* tests for running the commit editor, and fix problem of not passing in
31
* Merging add of a new file clashing with an existing file doesn't
32
work; add gets an error that it's already versioned and the merge
35
* Merge should ignore the destination's working directory, otherwise
36
we get an error about the statcache when pulling from a remote
39
20
* Add of a file that was present in the base revision should put back
40
21
the previous file-id.
42
* Not sure I'm happy with needing to pass a root id to EmptyTree;
43
comparing anything against an EmptyTree with no root should have the
46
23
* Handle diff of files which do not have a trailing newline; probably
47
24
requires patching difflib to get it exactly right, or otherwise
48
25
calling out to GNU diff.
50
* Should be able to copy files between branches to preserve their
51
file-id (and perhaps eventually parentage.)
27
* Import ElementTree update patch.
29
* Syntax should be ``bzr export -r REV``.
31
* Plugins that provide commands. By just installing a file into some
32
directory (e.g. ``/usr/share/bzr/plugins``) it should be possible to
33
create new top-level commands (``bzr frob``). Extensions can be
34
written in either Python (in which case they use the bzrlib API) or
35
in a separate process (in sh, C, whatever). It should be possible
36
to get help for plugin commands.
38
* Smart rewrap text in help messages to fit in $COLUMNS (or equivalent
53
41
* -r option should take a revision-id as well as a revno.
43
* ``bzr info`` could show space used by working tree, versioned files,
44
unknown and ignored files.
55
46
* ``bzr info`` should count only people with distinct email addresses as
56
47
different committers. (Or perhaps only distinct userids?)
71
64
__ http://mail.python.org/pipermail/python-list/2001-April/037847.html
66
* Read and write locks on branch while it's open.
73
68
* Separate read and write version checks?
75
* ``bzr status DIR`` should give status on all files under that
78
* ``bzr log DIR`` should give changes to any files within DIR; at the
79
moment it only lists things which modify the specific named file
80
(and not its contents)
70
* ``bzr status FILE...``
72
* Check all commands have decent help.
74
* Autogenerate argument/option help.
82
76
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
83
77
giving options to display ids, types, etc.
85
* RemoteBranch could maintain a cache either in memory or on disk. We
86
know more than an external cache might about which files are
87
immutable and which can vary. On the other hand, it's much simpler
88
to just use an external proxy cache.
90
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
91
~/.arch-cache, containing revision information encoded almost as a
92
bunch of archives. Perhaps we could simply store full paths.
94
* Maybe also store directories in the statcache so that we can quickly
95
identify that they still exist.
97
* Diff should show timestamps; for files from the working directory we
98
can use the file itself; for files from a revision we should use the
99
commit time of the revision.
101
* Perhaps split command infrastructure from the actual command
104
* Cleaner support for negative boolean options like --no-recurse.
106
* Statcache should possibly map all file paths to / separators
108
* quotefn doubles all backslashes on Windows; this is probably not the
109
best thing to do. What would be a better way to safely represent
110
filenames? Perhaps we could doublequote things containing spaces,
111
on the principle that filenames containing quotes are unlikely?
112
Nice for humans; less good for machine parsing.
114
* Patches should probably use only forward slashes, even on Windows,
115
otherwise Unix patch can't apply them. (?)
117
* Branch.update_revisions() inefficiently fetches revisions from the
118
remote server twice; once to find out what text and inventory they
119
need and then again to actually get the thing. This is a bit
122
One complicating factor here is that we don't really want to have
123
revisions present in the revision-store until all their constituent
124
parts are also stored.
126
The basic problem is that RemoteBranch.get_revision() and similar
127
methods return object, but what we really want is the raw XML, which
128
can be popped into our own store. That needs to be refactored.
130
* Guard against repeatedly merging any particular patch.
132
* More options for diff:
134
- diff two revisions of the same tree
136
- diff two different branches, optionally at different revisions
138
- diff a particular file in another tree against the corresponding
139
version in this tree (which should be the default if the second
140
parameter is a tree root)
142
- diff everything under a particular directory, in any of the above
145
- diff two files inside the same tree, even if they have different
148
- and, of course, tests for all this
150
* Reproducible performance benchmark to measure whether performance is
151
getting better or worse.
153
* ``bzr log -m foo`` should perhaps error if nothing matches?
155
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
157
If diffing between two branches then we probably want two -r
158
options, since the revisions don't form a range that can be
159
evaluated on either one.
161
* bzr diff shouldn't diff binary files
163
* setup.py install when run from a bzr tree should freeze the tree
164
revision-id into the installed bzr.
166
* bzr script should trap ImportError and perhaps give a better error
169
* revert after a merge should possibly remove all the BASE/THIS/OTHER
170
files to get you back to where you were.
172
* files that are added and then deleted are still reported as added
174
* stores should raise KeyError, not IndexError
176
* merging from a remote branch seems to sometimes raise errors not
179
* should be possible to give a related branch when pulling from a
180
remote branch to make things faster
182
* sometimes gives "conflicting add" even when the contents are in fact
185
* BZRDIR should be in branch.py not __init__.py.
187
* bzrlib.delta.compare_trees() shouldn't need to sort all of the result
188
lists, since they are being added in alphabetical order. Write tests
189
to guarantee this, and remove the sort() calls.
79
* Atomic file class that renames into place when it's closed.
194
* merge should add all revision and inventory XML to the local store.
196
* check should give a warning for revisions that are named in the
197
chain but not actually present in the store.
199
* remove anything outside of the branch implementation that directly
202
* More efficient diff of only selected files. We should be able to
203
just get the id for the selected files, look up their location and
204
diff just those files. No need to traverse the entire inventories.
85
* Display command grammar in help messages rather than hardcoding it.
87
* Change command functions into Command() objects, like in hct, and
88
then the grammar can be described directly in there. Since all
89
option definitions are global we can define them just once and
90
reference them from each command.
92
* Selective commit of only some files.
96
Status should be handled differently because it needs to report on
97
deleted and unknown files. diff only needs to deal with versioned
100
* Merge Aaron's merge code.
102
* Merge revert patch.
104
* Turn on stat cache code, and add optimization about avoiding
105
dangerous cache entries.
107
* ``bzr mv`` that does either rename or move as in Unix.
109
* More efficient diff of only selected files.
206
111
* Fix up Inventory objects to represent root object as an entry.
208
* Don't convert entire entry from ElementTree to an object when it is
209
read in, but rather wait until the program actually wants to know
113
* Don't convert entire entry from
212
115
* Extract changes from one revision to the next to a text form
213
116
suitable for transmission over email.
215
118
* More test cases.
217
- ``missing`` command
219
- Selected-file commit
221
- Impossible selected-file commit: adding things in non-versioned
222
directories, crossing renames, etc.
224
120
* Write a reproducible benchmark, perhaps importing various kernel versions.
122
* Change test.sh from Bourne shell into something in pure Python so
123
that it can be more portable.
226
125
* Directly import diffs! It seems a bit redundant to need to rescan
227
126
the directory to work out what files diff added/deleted/changed when
228
127
all the information is there in the diff in the first place.
278
177
if the subdirectory is not already versioned. Perhaps also require
279
178
a ``--nested`` to protect against confusion.
283
* More test framework:
285
- Class that describes the state of a working tree so we can just
288
* Try using XSLT to add some formatting to REST-generated HTML. Or
289
maybe write a small Python program that specifies a header and foot
290
for the pages and calls into the docutils libraries.
292
* --format=xml for log, status and other commands.
294
* Attempting to explicitly add a file that's already added should give
295
a warning; however there should be no warning for directories (since
296
we scan for new children) or files encountered in a directory that's
299
* Better handling of possible collisions on case-losing filesystems;
300
make sure a single file does not get added twice under different
303
* Clean up XML inventory:
305
- Use nesting rather than parent_id pointers.
307
- Hold the ElementTree in memory in the Inventory object and work
308
directly on that, rather than converting into Python objects every
309
time it is read in. Probably still expose it through some kind of
310
object interface though, but perhaps that should just be a proxy
313
- Less special cases for the root directory.
315
* Perhaps inventories should remember the revision in which each file
316
was last changed, as well as its current state? This is a bit
317
redundant but might often be interested to know.
319
* stat cache should perhaps only stat files as necessary, rather than
320
doing them all up-front. On the other hand, that disallows the
321
optimization of stating them in inode order.
323
* It'd be nice to pipeline multiple HTTP requests. Often we can
324
predict what will be wanted in future: all revisions, or all texts
325
in a particular revision, etc.
327
urlgrabber's docs say they are working on batched downloads; we
328
could perhaps ride on that or just create a background thread (ew).
330
* Paranoid mode where we never trust SHA-1 matches.
332
* --dry-run mode for commit? (Or maybe just run with
333
check-command=false?)
335
* Generally, be a bit more verbose unless --silent is specified.
337
* Function that finds all changes to files under a given directory;
338
perhaps log should use this if a directory is given.
340
* XML attributes might have trouble with filenames containing \n and
341
\r. Do we really want to support this? I think perhaps not.
343
* Unify smart_add and plain Branch.add(); perhaps smart_add should
344
just build a list of files to add and pass that to the regular add
347
* Function to list a directory, saying in which revision each file was
348
last modified. Useful for web and GUI interfaces, and slow to
349
compute one file at a time.
351
This will be done when we track file texts by referring to the
352
version that created them.
354
* Check locking is correct during merge-related operations.
356
* Perhaps attempts to get locks should timeout after some period of
357
time, or at least display a progress message.
359
* Don't pass around command classes but rather pass objects. This'd
360
make it cleaner to construct objects wrapping external commands.
362
* Track all merged-in revisions in a versioned add-only metafile.
364
* ``uncommit`` command that removes a revision from the end of the
365
revision-history; just doing this is enough to remove the commit,
366
and a new commit will automatically be made against the
367
predecessor. This can be repeated.
369
It only makes sense to delete from the tail of history.
371
This has been implemented, but it does not remove the texts from
added
removed
TODO
