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
20
* Fix tests so that import errors caused by modules don't produce false reports
21
that the tests themselves don't exist.
25
2005-11-05 mbp Flowers for stephane
23
* Fix tests so that one test failure doesn't prevent other tests from running
27
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
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:
220
199
just get the id for the selected files, look up their location and
221
200
diff just those files. No need to traverse the entire inventories.
223
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
224
under that directory.
226
202
* Fix up Inventory objects to represent root object as an entry.
228
204
* Don't convert entire entry from ElementTree to an object when it is
305
281
- Class that describes the state of a working tree so we can just
306
282
assert it's equal.
308
* There are too many methods on Branch() that really manipulate the
309
WorkingTree. They should be moved across.
311
Also there are some methods which are duplicated on Tree and
312
Inventory objects, and it should be made more clear which ones are
313
proxies and which ones behave differently, and how.
315
284
* Try using XSLT to add some formatting to REST-generated HTML. Or
316
285
maybe write a small Python program that specifies a header and foot
317
286
for the pages and calls into the docutils libraries.
334
303
- Hold the ElementTree in memory in the Inventory object and work
335
304
directly on that, rather than converting into Python objects every
336
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
337
306
object interface though, but perhaps that should just be a proxy
338
307
for the elements.
346
315
* stat cache should perhaps only stat files as necessary, rather than
347
316
doing them all up-front. On the other hand, that disallows the
348
opimization of stating them in inode order.
317
optimization of stating them in inode order.
350
319
* It'd be nice to pipeline multiple HTTP requests. Often we can
351
320
predict what will be wanted in future: all revisions, or all texts
369
336
* XML attributes might have trouble with filenames containing \n and
370
337
\r. Do we really want to support this? I think perhaps not.
372
* Remember execute bits, so that exports will work OK.
374
339
* Unify smart_add and plain Branch.add(); perhaps smart_add should
375
340
just build a list of files to add and pass that to the regular add
378
343
* Function to list a directory, saying in which revision each file was
379
last modified. Useful for web and gui interfaces, and slow to
344
last modified. Useful for web and GUI interfaces, and slow to
380
345
compute one file at a time.
382
347
This will be done when we track file texts by referring to the
387
352
* Perhaps attempts to get locks should timeout after some period of
388
353
time, or at least display a progress message.
390
* Split out upgrade functionality from check command into a separate
393
355
* Don't pass around command classes but rather pass objects. This'd
394
356
make it cleaner to construct objects wrapping external commands.
396
358
* Track all merged-in revisions in a versioned add-only metafile.
398
* ``pull --clobber`` should discard any local changes not present
399
remotely. Not generally what you want, but possibly useful when
400
you're just mirroring another branch and want to keep tracking it
401
even when they e.g. uncommit or make similar non-forward movements.
402
Also for push I suppose. Clobber may not be the best name, maybe
405
360
* ``uncommit`` command that removes a revision from the end of the
406
361
revision-history; just doing this is enough to remove the commit,
407
362
and a new commit will automatically be made against the
408
363
predecessor. This can be repeated.
410
It only makes sense to delete from the tail of history, not from the
413
The revision, its inventory and texts remain floating in the store.
414
We should perhaps add the revision to a list of removed-commits, so
415
that it can be restored or at least accounted for when checking
416
consistency. This file would not be versioned, and probably should
417
not propagate when branched.
419
If we track merged revisions then we need to update this list too.
420
If the list is stored in a weave it's easy (implicit): the version
421
of the list can remain but it won't be referenced anymore. It's
422
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
489
434
with removing the tags on the way back in.
441
* Write some benchmark tests
443
* we could display the ids of some tests selected by time to rune, or cputime,
446
* We could run tests multiple times and report deviation/slowest/fastest.
448
* Gather lsprofile output for each test individually - log that somewhere.
450
* Should plugins be able to offer benchmark tests ?
added
removed
TODO
