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
20
* Add of a file that was present in the base revision should put back
29
21
the previous file-id.
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
23
* Handle diff of files which do not have a trailing newline; probably
36
24
requires patching difflib to get it exactly right, or otherwise
37
25
calling out to GNU diff.
39
* Should be able to copy files between branches to preserve their
40
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
42
39
* -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.
41
* ``bzr info`` could show space used by working tree, versioned files,
42
unknown and ignored files.
46
44
* ``bzr info`` should count only people with distinct email addresses as
47
45
different committers. (Or perhaps only distinct userids?)
81
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.
83
90
* RemoteBranch could maintain a cache either in memory or on disk. We
84
91
know more than an external cache might about which files are
85
92
immutable and which can vary. On the other hand, it's much simpler
86
93
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
* quotefn doubles all backslashes on Windows; this is probably not the
107
best thing to do. What would be a better way to safely represent
108
filenames? Perhaps we could doublequote things containing spaces,
109
on the principle that filenames containing quotes are unlikely?
110
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
* Branch.update_revisions() inefficiently fetches revisions from the
116
remote server twice; once to find out what text and inventory they
117
need and then again to actually get the thing. This is a bit
120
One complicating factor here is that we don't really want to have
121
revisions present in the revision-store until all their constituent
122
parts are also stored.
124
The basic problem is that RemoteBranch.get_revision() and similar
125
methods return object, but what we really want is the raw XML, which
126
can be popped into our own store. That needs to be refactored.
128
* ``bzr status FOO`` where foo is ignored should say so.
130
* ``bzr mkdir A...`` should just create and add A.
132
* Guard against repeatedly merging any particular patch.
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.
139
114
* Merge revert patch.
141
116
* ``bzr mv`` that does either rename or move as in Unix.
143
* More efficient diff of only selected files. We should be able to
144
just get the id for the selected files, look up their location and
145
diff just those files. No need to traverse the entire inventories.
147
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
148
under that directory.
118
* More efficient diff of only selected files.
150
120
* Fix up Inventory objects to represent root object as an entry.
152
* Don't convert entire entry from ElementTree to an object when it is
153
read in, but rather wait until the program actually wants to know
122
* Don't convert entire entry from
156
124
* Extract changes from one revision to the next to a text form
157
125
suitable for transmission over email.
159
127
* More test cases.
161
- Selected-file commit
163
- Impossible selected-file commit: adding things in non-versioned
164
directories, crossing renames, etc.
166
129
* 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.
168
134
* Directly import diffs! It seems a bit redundant to need to rescan
169
135
the directory to work out what files diff added/deleted/changed when
170
136
all the information is there in the diff in the first place.
273
239
doing them all up-front. On the other hand, that disallows the
274
240
opimization of stating them in inode order.
276
* It'd be nice to pipeline multiple HTTP requests. Often we can
277
predict what will be wanted in future: all revisions, or all texts
278
in a particular revision, etc.
280
urlgrabber's docs say they are working on batched downloads; we
281
could perhaps ride on that or just create a background thread (ew).
283
* Paranoid mode where we never trust SHA-1 matches.
285
* Don't commit if there are no changes unless forced.
287
* --dry-run mode for commit? (Or maybe just run with
288
check-command=false?)
290
* Generally, be a bit more verbose unless --silent is specified.
292
* Function that finds all changes to files under a given directory;
293
perhaps log should use this if a directory is given.
295
* XML attributes might have trouble with filenames containing \n and
296
\r. Do we really want to support this? I think perhaps not.
298
* Remember execute bits, so that exports will work OK.
300
* Unify smart_add and plain Branch.add(); perhaps smart_add should
301
just build a list of files to add and pass that to the regular add
304
* Function to list a directory, saying in which revision each file was
305
last modified. Useful for web and gui interfaces, and slow to
306
compute one file at a time.
308
* unittest is standard, but the results are kind of ugly; would be
309
nice to make it cleaner.
311
* Check locking is correct during merge-related operations.
313
* Perhaps attempts to get locks should timeout after some period of
314
time, or at least display a progress message.
316
* Split out upgrade functionality from check command into a separate
319
* Don't pass around command classes but rather pass objects. This'd
320
make it cleaner to construct objects wrapping external commands.
322
* Track all merged-in revisions in a versioned add-only metafile.
356
274
files, and respecting selective commits. Run the pre-commit check
357
275
(e.g. compile and run test suite) in there.
359
Possibly this should be done by splitting the commit function into
360
several parts (under a single interface). It is already rather
361
large. Decomposition:
363
- find tree modifications and prepare in-memory inventory
365
- export that inventory to a temporary directory
367
- run the test in that temporary directory
369
- if that succeeded, continue to actually finish the commit
371
What should be done with the text of modified files while this is
372
underway? I don't think we want to count on holding them in memory
373
and we can't trust the working files to stay in one place so I
374
suppose we need to move them into the text store, or otherwise into
375
a temporary directory.
377
If the commit does not actually complete, we would rather the
378
content was not left behind in the stores.
382
279
* GUI (maybe in Python GTK+?)
added
removed
TODO
