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 that 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
14
* Add of a file that was present in the base revision should put back
42
15
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
17
* Handle diff of files which do not have a trailing newline; probably
49
18
requires patching difflib to get it exactly right, or otherwise
50
19
calling out to GNU diff.
52
* Should be able to copy files between branches to preserve their
53
file-id (and perhaps eventually parentage.)
21
* Import ElementTree update patch.
23
* Syntax should be "bzr export -r REV".
27
* Plugins that provide commands. By just installing a file into some
28
directory (e.g. /usr/share/bzr/plugins) it should be possible to
29
create new top-level commands ("bzr frob"). Extensions can be
30
written in either Python (in which case they use the bzrlib API) or
31
in a separate process (in sh, C, whatever). It should be possible
32
to get help for plugin commands.
34
* Smart rewrap text in help messages to fit in $COLUMNS (or equivalent
55
37
* -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.
39
* "bzr info" could show space used by working tree, versioned files,
40
unknown and ignored files.
59
* ``bzr info`` should count only people with distinct email addresses as
42
* "bzr info" should count only people with distinct email addresses as
60
43
different committers. (Or perhaps only distinct userids?)
62
* On Windows, command-line arguments should be `glob-expanded`__,
45
* Tidier error for EPIPE: should be just "bzr: broken pipe" with no
46
other details because debugging information is rarely interesting.
48
* On Windows, command-line arguments should be glob-expanded__,
63
49
because the shell doesn't do this. However, there are probably some
64
50
commands where this shouldn't be done, such as 'bzr ignore', because
65
51
we want to accept globs.
67
* ``bzr ignore`` command that just adds a line to the ``.bzrignore`` file
68
and makes it versioned. Fix this to break symlinks.
70
* Any useful sanity checks in 'bzr ignore'? Perhaps give a warning if
71
they try to add a single file which is already versioned, or if they
72
add a pattern which already exists, or if it looks like they gave an
75
53
__ http://mail.python.org/pipermail/python-list/2001-April/037847.html
77
* 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)
86
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
87
giving options to display ids, types, etc.
89
* Split BzrError into various more specific subclasses for different
90
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
193
* stores should raise KeyError, not IndexError
195
* merging from a remote branch seems to sometimes raise errors not
198
* should be possible to give a related branch when pulling from a
199
remote branch to make things faster
201
* sometimes gives "conflicting add" even when the contents are in fact
204
* BZRDIR should be in branch.py not __init__.py.
206
* ``status `` should accept a -r option to show changes relative to a revision,
212
* ~/.bzr.log is not written anymore for some reason.
214
* merge should add all revision and inventory XML to the local store.
216
* check should give a warning for revisions that are named in the
217
chain but not actually present in the store.
219
* remove anything outside of the branch implementation that directly
222
* More efficient diff of only selected files. We should be able to
223
just get the id for the selected files, look up their location and
224
diff just those files. No need to traverse the entire inventories.
226
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
227
under that directory.
58
* Selective commit of only some files.
62
Status should be handled differently because it needs to report on
63
deleted and unknown files. diff only needs to deal with versioned
66
* Merge Aaron's merge code.
70
* Turn on stat cache code, and add optimization about avoiding
71
dangerous cache entries.
75
* More efficient diff of only selected files.
229
77
* Fix up Inventory objects to represent root object as an entry.
231
* Don't convert entire entry from ElementTree to an object when it is
232
read in, but rather wait until the program actually wants to know
79
* Don't convert entire entry from
235
81
* Extract changes from one revision to the next to a text form
236
82
suitable for transmission over email.
238
84
* More test cases.
240
- ``missing`` command
242
- Selected-file commit
244
- Impossible selected-file commit: adding things in non-versioned
245
directories, crossing renames, etc.
247
86
* Write a reproducible benchmark, perhaps importing various kernel versions.
88
* Change test.sh from Bourne shell into something in pure Python so
89
that it can be more portable.
249
91
* Directly import diffs! It seems a bit redundant to need to rescan
250
92
the directory to work out what files diff added/deleted/changed when
251
93
all the information is there in the diff in the first place.
271
117
- perhaps a pattern that matches only directories or non-directories
273
* Consider using Python logging library as well as/instead of
276
* Commands should give some progress indication by default.
278
- But quieten this with ``--silent``.
280
* Change to using gettext message localization.
282
* Make a clearer separation between internal and external bzrlib
283
interfaces. Make internal interfaces use protected names. Write at
284
least some documentation for those APIs, probably as docstrings.
286
Consider using ZopeInterface definitions for the external interface;
287
I think these are already used in PyBaz. They allow automatic
288
checking of the interface but may be unfamiliar to general Python
289
developers, so I'm not really keen.
291
* Commands to dump out all command help into a manpage or HTML file or
294
* Handle symlinks in the working directory; at the very least it
295
should be possible for them to be present and ignored/unknown
296
without causing assertion failures.
298
Eventually symlinks should be versioned.
300
* Allow init in a subdirectory to create a nested repository, but only
301
if the subdirectory is not already versioned. Perhaps also require
302
a ``--nested`` to protect against confusion.
306
* More test framework:
308
- Class that describes the state of a working tree so we can just
311
* There are too many methods on Branch() that really manipulate the
312
WorkingTree. They should be moved across.
314
Also there are some methods which are duplicated on Tree and
315
Inventory objects, and it should be made more clear which ones are
316
proxies and which ones behave differently, and how.
318
* Try using XSLT to add some formatting to REST-generated HTML. Or
319
maybe write a small Python program that specifies a header and foot
320
for the pages and calls into the docutils libraries.
322
* --format=xml for log, status and other commands.
324
* Attempting to explicitly add a file that's already added should give
325
a warning; however there should be no warning for directories (since
326
we scan for new children) or files encountered in a directory that's
329
* Better handling of possible collisions on case-losing filesystems;
330
make sure a single file does not get added twice under different
333
* Clean up XML inventory:
335
- Use nesting rather than parent_id pointers.
337
- Hold the ElementTree in memory in the Inventory object and work
338
directly on that, rather than converting into Python objects every
339
time it is read in. Probably still exposoe it through some kind of
340
object interface though, but perhaps that should just be a proxy
343
- Less special cases for the root directory.
345
* Perhaps inventories should remember the revision in which each file
346
was last changed, as well as its current state? This is a bit
347
redundant but might often be interested to know.
349
* stat cache should perhaps only stat files as necessary, rather than
350
doing them all up-front. On the other hand, that disallows the
351
opimization of stating them in inode order.
353
* It'd be nice to pipeline multiple HTTP requests. Often we can
354
predict what will be wanted in future: all revisions, or all texts
355
in a particular revision, etc.
357
urlgrabber's docs say they are working on batched downloads; we
358
could perhaps ride on that or just create a background thread (ew).
360
* Paranoid mode where we never trust SHA-1 matches.
362
* Don't commit if there are no changes unless forced.
364
* --dry-run mode for commit? (Or maybe just run with
365
check-command=false?)
367
* Generally, be a bit more verbose unless --silent is specified.
369
* Function that finds all changes to files under a given directory;
370
perhaps log should use this if a directory is given.
372
* XML attributes might have trouble with filenames containing \n and
373
\r. Do we really want to support this? I think perhaps not.
375
* Remember execute bits, so that exports will work OK.
377
* Unify smart_add and plain Branch.add(); perhaps smart_add should
378
just build a list of files to add and pass that to the regular add
381
* Function to list a directory, saying in which revision each file was
382
last modified. Useful for web and gui interfaces, and slow to
383
compute one file at a time.
385
This will be done when we track file texts by referring to the
386
version that created them.
388
* Check locking is correct during merge-related operations.
390
* Perhaps attempts to get locks should timeout after some period of
391
time, or at least display a progress message.
393
* Split out upgrade functionality from check command into a separate
396
* Don't pass around command classes but rather pass objects. This'd
397
make it cleaner to construct objects wrapping external commands.
399
* Track all merged-in revisions in a versioned add-only metafile.
401
* ``pull --clobber`` should discard any local changes not present
402
remotely. Not generally what you want, but possibly useful when
403
you're just mirroring another branch and want to keep tracking it
404
even when they e.g. uncommit or make similar non-forward movements.
405
Also for push I suppose. Clobber may not be the best name, maybe
408
* ``uncommit`` command that removes a revision from the end of the
409
revision-history; just doing this is enough to remove the commit,
410
and a new commit will automatically be made against the
411
predecessor. This can be repeated.
413
It only makes sense to delete from the tail of history, not from the
416
The revision, its inventory and texts remain floating in the store.
417
We should perhaps add the revision to a list of removed-commits, so
418
that it can be restored or at least accounted for when checking
419
consistency. This file would not be versioned, and probably should
420
not propagate when branched.
422
If we track merged revisions then we need to update this list too.
423
If the list is stored in a weave it's easy (implicit): the version
424
of the list can remain but it won't be referenced anymore. It's
425
probably best to just store this list in a weave in the first place
119
* Expansion of $Id$ keywords within working files. Perhaps do this in
120
exports first as a simpler case because then we don't need to deal
121
with removing the tags on the way back in.
432
* Generate annotations from current file relative to previous
435
- Is it necessary to store any kind of annotation where data was
438
* Update revfile_ format and make it active:
440
- Texts should be identified by something keyed on the revision, not
441
an individual text-id. This is much more useful for annotate I
442
think; we want to map back to the revision that last changed it.
444
- Access revfile revisions through the Tree/Store classes.
446
- Check them from check commands.
450
.. _revfile: revfile.html
452
127
* Hooks for pre-commit, post-commit, etc.
454
129
Consider the security implications; probably should not enable hooks
added
removed
TODO
