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
20
* Fix tests so that import errors caused by modules don't produce false reports
21
that the tests themselves don't exist.
23
* Fix tests so that one test failure doesn't prevent other tests from running
25
* print a message at the end of running the tests telling them that the
28
26
test log and output exists but can be removed
30
28
* tests for running the commit editor, and fix problem of not passing in
55
53
* -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.
59
55
* ``bzr info`` should count only people with distinct email addresses as
60
56
different committers. (Or perhaps only distinct userids?)
86
82
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
87
83
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
85
* RemoteBranch could maintain a cache either in memory or on disk. We
99
86
know more than an external cache might about which files are
100
87
immutable and which can vary. On the other hand, it's much simpler
140
127
methods return object, but what we really want is the raw XML, which
141
128
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
130
* Guard against repeatedly merging any particular patch.
149
132
* More options for diff:
217
199
just get the id for the selected files, look up their location and
218
200
diff just those files. No need to traverse the entire inventories.
220
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
221
under that directory.
223
202
* Fix up Inventory objects to represent root object as an entry.
225
204
* Don't convert entire entry from ElementTree to an object when it is
302
281
- Class that describes the state of a working tree so we can just
303
282
assert it's equal.
305
* There are too many methods on Branch() that really manipulate the
306
WorkingTree. They should be moved across.
308
Also there are some methods which are duplicated on Tree and
309
Inventory objects, and it should be made more clear which ones are
310
proxies and which ones behave differently, and how.
312
284
* Try using XSLT to add some formatting to REST-generated HTML. Or
313
285
maybe write a small Python program that specifies a header and foot
314
286
for the pages and calls into the docutils libraries.
331
303
- Hold the ElementTree in memory in the Inventory object and work
332
304
directly on that, rather than converting into Python objects every
333
time it is read in. Probably still exposoe it through some kind of
305
time it is read in. Probably still expose it through some kind of
334
306
object interface though, but perhaps that should just be a proxy
335
307
for the elements.
343
315
* stat cache should perhaps only stat files as necessary, rather than
344
316
doing them all up-front. On the other hand, that disallows the
345
opimization of stating them in inode order.
317
optimization of stating them in inode order.
347
319
* It'd be nice to pipeline multiple HTTP requests. Often we can
348
320
predict what will be wanted in future: all revisions, or all texts
366
336
* XML attributes might have trouble with filenames containing \n and
367
337
\r. Do we really want to support this? I think perhaps not.
369
* Remember execute bits, so that exports will work OK.
371
339
* Unify smart_add and plain Branch.add(); perhaps smart_add should
372
340
just build a list of files to add and pass that to the regular add
375
343
* Function to list a directory, saying in which revision each file was
376
last modified. Useful for web and gui interfaces, and slow to
344
last modified. Useful for web and GUI interfaces, and slow to
377
345
compute one file at a time.
379
347
This will be done when we track file texts by referring to the
384
352
* Perhaps attempts to get locks should timeout after some period of
385
353
time, or at least display a progress message.
387
* Split out upgrade functionality from check command into a separate
390
355
* Don't pass around command classes but rather pass objects. This'd
391
356
make it cleaner to construct objects wrapping external commands.
393
358
* Track all merged-in revisions in a versioned add-only metafile.
395
* ``pull --clobber`` should discard any local changes not present
396
remotely. Not generally what you want, but possibly useful when
397
you're just mirroring another branch and want to keep tracking it
398
even when they e.g. uncommit or make similar non-forward movements.
399
Also for push I suppose. Clobber may not be the best name, maybe
402
360
* ``uncommit`` command that removes a revision from the end of the
403
361
revision-history; just doing this is enough to remove the commit,
404
362
and a new commit will automatically be made against the
405
363
predecessor. This can be repeated.
407
It only makes sense to delete from the tail of history, not from the
410
The revision, its inventory and texts remain floating in the store.
411
We should perhaps add the revision to a list of removed-commits, so
412
that it can be restored or at least accounted for when checking
413
consistency. This file would not be versioned, and probably should
414
not propagate when branched.
416
If we track merged revisions then we need to update this list too.
417
If the list is stored in a weave it's easy (implicit): the version
418
of the list can remain but it won't be referenced anymore. It's
419
probably best to just store this list in a weave in the first place
365
It only makes sense to delete from the tail of history.
367
This has been implemented, but it does not remove the texts from
added
removed
TODO
