20
* is_within_any is very very dodgy
22
* Merging add of a new file clashing with an existing file doesn't
23
work; add gets an error that it's already versioned and the merge
26
* Merge should ignore the destination's working directory, otherwise
27
we get an error about the statcache when pulling from a remote
20
30
* Add of a file that was present in the base revision should put back
21
31
the previous file-id.
33
* Not sure I'm happy with needing to pass a root id to EmptyTree;
34
comparing anything against an EmptyTree with no root should have the
23
37
* Handle diff of files which do not have a trailing newline; probably
24
38
requires patching difflib to get it exactly right, or otherwise
25
39
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
41
* Should be able to copy files between branches to preserve their
42
file-id (and perhaps eventually parentage.)
39
44
* -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.
46
* allow ``bzr st -r 300`` to show a summary of changes since then.
44
48
* ``bzr info`` should count only people with distinct email addresses as
45
49
different committers. (Or perhaps only distinct userids?)
81
81
temporary directory and then tar that up.)
83
83
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
85
* testbzr should by default test the bzr binary in the same directory
86
as the testbzr script, or take a path to it as a first parameter.
88
Should show the version from bzr and the path name.
90
85
* RemoteBranch could maintain a cache either in memory or on disk. We
91
86
know more than an external cache might about which files are
92
87
immutable and which can vary. On the other hand, it's much simpler
93
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
* ``bzr status FOO`` where foo is ignored should say so.
132
* ``bzr mkdir A...`` should just create and add A.
134
* Guard against repeatedly merging any particular patch.
136
* More options for diff:
138
- diff two revisions of the same tree
140
- diff two different branches, optionally at different revisions
142
- diff a particular file in another tree against the corresponding
143
version in this tree (which should be the default if the second
144
parameter is a tree root)
146
- diff everything under a particular directory, in any of the above
149
- diff two files inside the same tree, even if they have different
152
- and, of course, tests for all this
154
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
156
* Reproducible performance benchmark to measure whether performance is
157
getting better or worse.
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
* Selective commit of only some files.
106
* Faster diff/status.
108
Status should be handled differently because it needs to report on
109
deleted and unknown files. diff only needs to deal with versioned
112
* Merge Aaron's merge code.
114
163
* Merge revert patch.
116
165
* ``bzr mv`` that does either rename or move as in Unix.
118
* More efficient diff of only selected files.
167
* More efficient diff of only selected files. We should be able to
168
just get the id for the selected files, look up their location and
169
diff just those files. No need to traverse the entire inventories.
171
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
172
under that directory.
120
174
* Fix up Inventory objects to represent root object as an entry.
122
* Don't convert entire entry from
176
* Don't convert entire entry from ElementTree to an object when it is
177
read in, but rather wait until the program actually wants to know
124
180
* Extract changes from one revision to the next to a text form
125
181
suitable for transmission over email.
127
183
* More test cases.
185
- Selected-file commit
187
- Impossible selected-file commit: adding things in non-versioned
188
directories, crossing renames, etc.
129
190
* Write a reproducible benchmark, perhaps importing various kernel versions.
131
* Change test.sh from Bourne shell into something in pure Python so
132
that it can be more portable.
134
192
* Directly import diffs! It seems a bit redundant to need to rescan
135
193
the directory to work out what files diff added/deleted/changed when
136
194
all the information is there in the diff in the first place.
242
300
* It'd be nice to pipeline multiple HTTP requests. Often we can
243
301
predict what will be wanted in future: all revisions, or all texts
244
in a particular revision, etc.
302
in a particular revision, etc.
246
304
urlgrabber's docs say they are working on batched downloads; we
247
305
could perhaps ride on that or just create a background thread (ew).
249
* Should be a signature at the top of the cache file.
251
307
* Paranoid mode where we never trust SHA-1 matches.
309
* Don't commit if there are no changes unless forced.
311
* --dry-run mode for commit? (Or maybe just run with
312
check-command=false?)
314
* Generally, be a bit more verbose unless --silent is specified.
316
* Function that finds all changes to files under a given directory;
317
perhaps log should use this if a directory is given.
319
* XML attributes might have trouble with filenames containing \n and
320
\r. Do we really want to support this? I think perhaps not.
322
* Remember execute bits, so that exports will work OK.
324
* Unify smart_add and plain Branch.add(); perhaps smart_add should
325
just build a list of files to add and pass that to the regular add
328
* Function to list a directory, saying in which revision each file was
329
last modified. Useful for web and gui interfaces, and slow to
330
compute one file at a time.
332
* unittest is standard, but the results are kind of ugly; would be
333
nice to make it cleaner.
335
* Check locking is correct during merge-related operations.
337
* Perhaps attempts to get locks should timeout after some period of
338
time, or at least display a progress message.
340
* Split out upgrade functionality from check command into a separate
343
* Don't pass around command classes but rather pass objects. This'd
344
make it cleaner to construct objects wrapping external commands.
346
* Track all merged-in revisions in a versioned add-only metafile.
285
380
files, and respecting selective commits. Run the pre-commit check
286
381
(e.g. compile and run test suite) in there.
383
Possibly this should be done by splitting the commit function into
384
several parts (under a single interface). It is already rather
385
large. Decomposition:
387
- find tree modifications and prepare in-memory inventory
389
- export that inventory to a temporary directory
391
- run the test in that temporary directory
393
- if that succeeded, continue to actually finish the commit
395
What should be done with the text of modified files while this is
396
underway? I don't think we want to count on holding them in memory
397
and we can't trust the working files to stay in one place so I
398
suppose we need to move them into the text store, or otherwise into
399
a temporary directory.
401
If the commit does not actually complete, we would rather the
402
content was not left behind in the stores.
290
406
* GUI (maybe in Python GTK+?)
added
removed
TODO
