1
.. -*- mode: indented-text; compile-command: "make -C doc" -*-
9
See also various low-level TODOs in the source code. Try looking in
10
the list archive or on gmane.org for previous discussion of these
13
These are classified by approximate size: an hour or less, a day or
14
less, and several days or more.
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
* Add of a file that was present in the base revision should put back
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
* Handle diff of files which do not have a trailing newline; probably
36
requires patching difflib to get it exactly right, or otherwise
37
calling out to GNU diff.
39
* Should be able to copy files between branches to preserve their
40
file-id (and perhaps eventually parentage.)
42
* -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.
46
* ``bzr info`` should count only people with distinct email addresses as
47
different committers. (Or perhaps only distinct userids?)
49
* On Windows, command-line arguments should be `glob-expanded`__,
50
because the shell doesn't do this. However, there are probably some
51
commands where this shouldn't be done, such as 'bzr ignore', because
52
we want to accept globs.
54
* ``bzr ignore`` command that just adds a line to the ``.bzrignore`` file
55
and makes it versioned. Fix this to break symlinks.
57
* Any useful sanity checks in 'bzr ignore'? Perhaps give a warning if
58
they try to add a single file which is already versioned, or if they
59
add a pattern which already exists, or if it looks like they gave an
62
__ http://mail.python.org/pipermail/python-list/2001-April/037847.html
64
* Separate read and write version checks?
66
* ``bzr status DIR`` should give status on all files under that
69
* ``bzr log DIR`` should give changes to any files within DIR.
71
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
72
giving options to display ids, types, etc.
74
* Split BzrError into various more specific subclasses for different
75
errors people might want to catch.
77
* If the export destination ends in '.tar', '.tar.gz', etc then create
78
a tarball instead of a directory. (Need to actually make a
79
temporary directory and then tar that up.)
81
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
83
* RemoteBranch could maintain a cache either in memory or on disk. We
84
know more than an external cache might about which files are
85
immutable and which can vary. On the other hand, it's much simpler
86
to just use an external proxy cache.
88
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
89
~/.arch-cache, containing revision information encoded almost as a
90
bunch of archives. Perhaps we could simply store full paths.
92
* Maybe also store directories in the statcache so that we can quickly
93
identify that they still exist.
95
* Diff should show timestamps; for files from the working directory we
96
can use the file itself; for files from a revision we should use the
97
commit time of the revision.
99
* Perhaps split command infrastructure from the actual command
102
* Cleaner support for negative boolean options like --no-recurse.
104
* Statcache should possibly map all file paths to / separators
106
1
* quotefn doubles all backslashes on Windows; this is probably not the
107
2
best thing to do. What would be a better way to safely represent
108
3
filenames? Perhaps we could doublequote things containing spaces,
109
4
on the principle that filenames containing quotes are unlikely?
110
5
Nice for humans; less good for machine parsing.
112
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
115
7
* Branch.update_revisions() inefficiently fetches revisions from the
116
8
remote server twice; once to find out what text and inventory they
117
9
need and then again to actually get the thing. This is a bit
150
38
- 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 .``
40
* Reproducible performance benchmark to measure whether performance is
41
getting better or worse.
43
* ``bzr log -m foo`` should perhaps error if nothing matches?
45
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
47
If diffing between two branches then we probably want two -r
48
options, since the revisions don't form a range that can be
49
evaluated on either one.
51
* bzr diff shouldn't diff binary files
53
* setup.py install when run from a bzr tree should freeze the tree
54
revision-id into the installed bzr.
56
* bzr script should trap ImportError and perhaps give a better error
59
* revert after a merge should possibly remove all the BASE/THIS/OTHER
60
files to get you back to where you were.
62
* files that are added and then deleted are still reported as added
64
* stores should raise KeyError, not IndexError
66
* merging from a remote branch seems to sometimes raise errors not
69
* should be possible to give a related branch when pulling from a
70
remote branch to make things faster
72
* sometimes gives "conflicting add" even when the contents are in fact
75
* BZRDIR should be in branch.py not __init__.py.
77
* bzrlib.delta.compare_trees() shouldn't need to sort all of the result
78
lists, since they are being added in alphabetical order. Write tests
79
to guarantee this, and remove the sort() calls.
162
* Merge revert patch.
164
* ``bzr mv`` that does either rename or move as in Unix.
84
* merge should add all revision and inventory XML to the local store.
86
* check should give a warning for revisions that are named in the
87
chain but not actually present in the store.
89
* remove anything outside of the branch implementation that directly
166
92
* More efficient diff of only selected files. We should be able to
167
93
just get the id for the selected files, look up their location and
168
94
diff just those files. No need to traverse the entire inventories.
170
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
171
under that directory.
173
96
* Fix up Inventory objects to represent root object as an entry.
175
98
* Don't convert entire entry from ElementTree to an object when it is
318
230
* XML attributes might have trouble with filenames containing \n and
319
231
\r. Do we really want to support this? I think perhaps not.
321
* Remember execute bits, so that exports will work OK.
323
233
* Unify smart_add and plain Branch.add(); perhaps smart_add should
324
234
just build a list of files to add and pass that to the regular add
327
237
* Function to list a directory, saying in which revision each file was
328
last modified. Useful for web and gui interfaces, and slow to
238
last modified. Useful for web and GUI interfaces, and slow to
329
239
compute one file at a time.
331
* unittest is standard, but the results are kind of ugly; would be
332
nice to make it cleaner.
241
This will be done when we track file texts by referring to the
242
version that created them.
334
244
* Check locking is correct during merge-related operations.
336
246
* Perhaps attempts to get locks should timeout after some period of
337
247
time, or at least display a progress message.
339
* Split out upgrade functionality from check command into a separate
342
249
* Don't pass around command classes but rather pass objects. This'd
343
250
make it cleaner to construct objects wrapping external commands.
345
252
* Track all merged-in revisions in a versioned add-only metafile.
254
* ``uncommit`` command that removes a revision from the end of the
255
revision-history; just doing this is enough to remove the commit,
256
and a new commit will automatically be made against the
257
predecessor. This can be repeated.
259
It only makes sense to delete from the tail of history.
261
This has been implemented, but it does not remove the texts from
264
* ``bzrlib.lazy_import.lazy_import`` could check to see if a given
265
module has already been imported (look at ``sys.modules``). If it
266
has, then just import it directly, rather than creating a lazy
added
removed
TODO
