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
* print a message at the end of running the tests telling them tht the
28
test log and output exists but can be removed
30
* tests for running the commit editor, and fix problem of not passing in
33
* Merging add of a new file clashing with an existing file doesn't
34
work; add gets an error that it's already versioned and the merge
37
* Merge should ignore the destination's working directory, otherwise
38
we get an error about the statcache when pulling from a remote
41
20
* Add of a file that was present in the base revision should put back
42
21
the previous file-id.
44
* Not sure I'm happy with needing to pass a root id to EmptyTree;
45
comparing anything against an EmptyTree with no root should have the
48
23
* Handle diff of files which do not have a trailing newline; probably
49
24
requires patching difflib to get it exactly right, or otherwise
50
25
calling out to GNU diff.
52
* Should be able to copy files between branches to preserve their
53
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
55
41
* -r option should take a revision-id as well as a revno.
57
* allow ``bzr st -r 300`` to show a summary of changes since then.
43
* ``bzr info`` could show space used by working tree, versioned files,
44
unknown and ignored files.
59
46
* ``bzr info`` should count only people with distinct email addresses as
60
47
different committers. (Or perhaps only distinct userids?)
75
64
__ http://mail.python.org/pipermail/python-list/2001-April/037847.html
66
* Read and write locks on branch while it's open.
77
68
* Separate read and write version checks?
79
* ``bzr status DIR`` should give status on all files under that
82
* ``bzr log DIR`` should give changes to any files within DIR; at the
83
moment it only lists things which modify the specific named file
84
(and not its contents)
70
* ``bzr status FILE...``
72
* Check all commands have decent help.
74
* Autogenerate argument/option help.
86
76
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
87
77
giving options to display ids, types, etc.
79
* Atomic file class that renames into place when it's closed.
81
* Don't abort if ``~/.bzr.log`` can't be used.
89
83
* Split BzrError into various more specific subclasses for different
90
84
errors people might want to catch.
92
* If the export destination ends in '.tar', '.tar.gz', etc then create
93
a tarball instead of a directory. (Need to actually make a
94
temporary directory and then tar that up.)
96
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
98
* RemoteBranch could maintain a cache either in memory or on disk. We
99
know more than an external cache might about which files are
100
immutable and which can vary. On the other hand, it's much simpler
101
to just use an external proxy cache.
103
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
104
~/.arch-cache, containing revision information encoded almost as a
105
bunch of archives. Perhaps we could simply store full paths.
107
* Maybe also store directories in the statcache so that we can quickly
108
identify that they still exist.
110
* Diff should show timestamps; for files from the working directory we
111
can use the file itself; for files from a revision we should use the
112
commit time of the revision.
114
* Perhaps split command infrastructure from the actual command
117
* Cleaner support for negative boolean options like --no-recurse.
119
* Statcache should possibly map all file paths to / separators
121
* quotefn doubles all backslashes on Windows; this is probably not the
122
best thing to do. What would be a better way to safely represent
123
filenames? Perhaps we could doublequote things containing spaces,
124
on the principle that filenames containing quotes are unlikely?
125
Nice for humans; less good for machine parsing.
127
* Patches should probably use only forward slashes, even on Windows,
128
otherwise Unix patch can't apply them. (?)
130
* Branch.update_revisions() inefficiently fetches revisions from the
131
remote server twice; once to find out what text and inventory they
132
need and then again to actually get the thing. This is a bit
135
One complicating factor here is that we don't really want to have
136
revisions present in the revision-store until all their constituent
137
parts are also stored.
139
The basic problem is that RemoteBranch.get_revision() and similar
140
methods return object, but what we really want is the raw XML, which
141
can be popped into our own store. That needs to be refactored.
143
* ``bzr status FOO`` where foo is ignored should say so.
145
* ``bzr mkdir A...`` should just create and add A.
147
* Guard against repeatedly merging any particular patch.
149
* More options for diff:
151
- diff two revisions of the same tree
153
- diff two different branches, optionally at different revisions
155
- diff a particular file in another tree against the corresponding
156
version in this tree (which should be the default if the second
157
parameter is a tree root)
159
- diff everything under a particular directory, in any of the above
162
- diff two files inside the same tree, even if they have different
165
- and, of course, tests for all this
167
* ``bzr add`` with no arguments should probably be the same as ``bzr add .``
169
* Reproducible performance benchmark to measure whether performance is
170
getting better or worse.
172
* ``bzr log -m foo`` should perhaps error if nothing matches?
174
* ``bzr diff -r 30 -r 40 foo.c`` or ``bzr diff -r30..40 foo.c``
176
If diffing between two branches then we probably want two -r
177
options, since the revisions don't form a range that can be
178
evaluated on either one.
180
* bzr diff shouldn't diff binary files
182
* setup.py install when run from a bzr tree should freeze the tree
183
revision-id into the installed bzr.
185
* bzr script should trap ImportError and perhaps give a better error
188
* revert after a merge should possibly remove all the BASE/THIS/OTHER
189
files to get you back to where you were.
191
* files that are added and then deleted are still reported as added
199
* merge should add all revision and inventory XML to the local store.
201
* check should give a warning for revisions that are named in the
202
chain but not actually present in the store.
204
* remove anything outside of the branch implementation that directly
207
* More efficient diff of only selected files. We should be able to
208
just get the id for the selected files, look up their location and
209
diff just those files. No need to traverse the entire inventories.
211
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
212
under that directory.
89
* Display command grammar in help messages rather than hardcoding it.
91
* Change command functions into Command() objects, like in hct, and
92
then the grammar can be described directly in there. Since all
93
option definitions are global we can define them just once and
94
reference them from each command.
96
* Selective commit of only some files.
100
Status should be handled differently because it needs to report on
101
deleted and unknown files. diff only needs to deal with versioned
104
* Merge Aaron's merge code.
106
* Merge revert patch.
108
* Turn on stat cache code, and add optimization about avoiding
109
dangerous cache entries.
111
* ``bzr mv`` that does either rename or move as in Unix.
113
* More efficient diff of only selected files.
214
115
* Fix up Inventory objects to represent root object as an entry.
216
* Don't convert entire entry from ElementTree to an object when it is
217
read in, but rather wait until the program actually wants to know
117
* Don't convert entire entry from
220
119
* Extract changes from one revision to the next to a text form
221
120
suitable for transmission over email.
223
122
* More test cases.
225
- Selected-file commit
227
- Impossible selected-file commit: adding things in non-versioned
228
directories, crossing renames, etc.
230
124
* Write a reproducible benchmark, perhaps importing various kernel versions.
126
* Change test.sh from Bourne shell into something in pure Python so
127
that it can be more portable.
232
129
* Directly import diffs! It seems a bit redundant to need to rescan
233
130
the directory to work out what files diff added/deleted/changed when
234
131
all the information is there in the diff in the first place.
309
210
we scan for new children) or files encountered in a directory that's
312
* Better handling of possible collisions on case-losing filesystems;
313
make sure a single file does not get added twice under different
316
* Clean up XML inventory:
318
- Use nesting rather than parent_id pointers.
320
- Hold the ElementTree in memory in the Inventory object and work
321
directly on that, rather than converting into Python objects every
322
time it is read in. Probably still exposoe it through some kind of
323
object interface though, but perhaps that should just be a proxy
326
- Less special cases for the root directory.
328
* Perhaps inventories should remember the revision in which each file
329
was last changed, as well as its current state? This is a bit
330
redundant but might often be interested to know.
332
* stat cache should perhaps only stat files as necessary, rather than
333
doing them all up-front. On the other hand, that disallows the
334
opimization of stating them in inode order.
336
* It'd be nice to pipeline multiple HTTP requests. Often we can
337
predict what will be wanted in future: all revisions, or all texts
338
in a particular revision, etc.
340
urlgrabber's docs say they are working on batched downloads; we
341
could perhaps ride on that or just create a background thread (ew).
343
* Paranoid mode where we never trust SHA-1 matches.
345
* Don't commit if there are no changes unless forced.
347
* --dry-run mode for commit? (Or maybe just run with
348
check-command=false?)
350
* Generally, be a bit more verbose unless --silent is specified.
352
* Function that finds all changes to files under a given directory;
353
perhaps log should use this if a directory is given.
355
* XML attributes might have trouble with filenames containing \n and
356
\r. Do we really want to support this? I think perhaps not.
358
* Remember execute bits, so that exports will work OK.
360
* Unify smart_add and plain Branch.add(); perhaps smart_add should
361
just build a list of files to add and pass that to the regular add
364
* Function to list a directory, saying in which revision each file was
365
last modified. Useful for web and gui interfaces, and slow to
366
compute one file at a time.
368
This will be done when we track file texts by referring to the
369
version that created them.
371
* Check locking is correct during merge-related operations.
373
* Perhaps attempts to get locks should timeout after some period of
374
time, or at least display a progress message.
376
* Split out upgrade functionality from check command into a separate
379
* Don't pass around command classes but rather pass objects. This'd
380
make it cleaner to construct objects wrapping external commands.
382
* Track all merged-in revisions in a versioned add-only metafile.
384
* ``pull --clobber`` should discard any local changes not present
385
remotely. Not generally what you want, but possibly useful when
386
you're just mirroring another branch and want to keep tracking it
387
even when they e.g. uncommit or make similar non-forward movements.
388
Also for push I suppose. Clobber may not be the best name, maybe
391
* ``uncommit`` command that removes a revision from the end of the
392
revision-history; just doing this is enough to remove the commit,
393
and a new commit will automatically be made against the
394
predecessor. This can be repeated.
396
It only makes sense to delete from the tail of history, not from the
399
The revision, its inventory and texts remain floating in the store.
400
We should perhaps add the revision to a list of removed-commits, so
401
that it can be restored or at least accounted for when checking
402
consistency. This file would not be versioned, and probably should
403
not propagate when branched.
405
If we track merged revisions then we need to update this list too.
406
If the list is stored in a weave it's easy (implicit): the version
407
of the list can remain but it won't be referenced anymore. It's
408
probably best to just store this list in a weave in the first place
added
removed
TODO
