20
* Fix tests so that import errors caused by modules don't produce false reports
21
that the tests themselves don't exist.
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
23
* Fix tests so that one test failure doesn't prevent other tests from running
25
2005-11-05 mbp Flowers for stephane
25
27
* print a message at the end of running the tests telling them that the
26
28
test log and output exists but can be removed
53
55
* -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.
55
59
* ``bzr info`` should count only people with distinct email addresses as
56
60
different committers. (Or perhaps only distinct userids?)
82
86
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
83
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
85
98
* RemoteBranch could maintain a cache either in memory or on disk. We
86
99
know more than an external cache might about which files are
87
100
immutable and which can vary. On the other hand, it's much simpler
127
140
methods return object, but what we really want is the raw XML, which
128
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.
130
147
* Guard against repeatedly merging any particular patch.
132
149
* More options for diff:
185
204
* BZRDIR should be in branch.py not __init__.py.
187
* bzrlib.delta.compare_trees() shouldn't need to sort all of the result
188
lists, since they are being added in alphabetical order. Write tests
189
to guarantee this, and remove the sort() calls.
206
* ``status `` should accept a -r option to show changes relative to a revision,
212
* ~/.bzr.log is not written anymore for some reason.
194
214
* merge should add all revision and inventory XML to the local store.
196
216
* check should give a warning for revisions that are named in the
203
223
just get the id for the selected files, look up their location and
204
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.
206
229
* Fix up Inventory objects to represent root object as an entry.
208
231
* Don't convert entire entry from ElementTree to an object when it is
285
308
- Class that describes the state of a working tree so we can just
286
309
assert it's equal.
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.
288
318
* Try using XSLT to add some formatting to REST-generated HTML. Or
289
319
maybe write a small Python program that specifies a header and foot
290
320
for the pages and calls into the docutils libraries.
307
337
- Hold the ElementTree in memory in the Inventory object and work
308
338
directly on that, rather than converting into Python objects every
309
time it is read in. Probably still expose it through some kind of
339
time it is read in. Probably still exposoe it through some kind of
310
340
object interface though, but perhaps that should just be a proxy
311
341
for the elements.
319
349
* stat cache should perhaps only stat files as necessary, rather than
320
350
doing them all up-front. On the other hand, that disallows the
321
optimization of stating them in inode order.
351
opimization of stating them in inode order.
323
353
* It'd be nice to pipeline multiple HTTP requests. Often we can
324
354
predict what will be wanted in future: all revisions, or all texts
340
372
* XML attributes might have trouble with filenames containing \n and
341
373
\r. Do we really want to support this? I think perhaps not.
375
* Remember execute bits, so that exports will work OK.
343
377
* Unify smart_add and plain Branch.add(); perhaps smart_add should
344
378
just build a list of files to add and pass that to the regular add
347
381
* Function to list a directory, saying in which revision each file was
348
last modified. Useful for web and GUI interfaces, and slow to
382
last modified. Useful for web and gui interfaces, and slow to
349
383
compute one file at a time.
351
385
This will be done when we track file texts by referring to the
356
390
* Perhaps attempts to get locks should timeout after some period of
357
391
time, or at least display a progress message.
393
* Split out upgrade functionality from check command into a separate
359
396
* Don't pass around command classes but rather pass objects. This'd
360
397
make it cleaner to construct objects wrapping external commands.
362
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
364
408
* ``uncommit`` command that removes a revision from the end of the
365
409
revision-history; just doing this is enough to remove the commit,
366
410
and a new commit will automatically be made against the
367
411
predecessor. This can be repeated.
369
It only makes sense to delete from the tail of history.
371
This has been implemented, but it does not remove the texts from
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
438
492
with removing the tags on the way back in.
445
* Write some benchmark tests
447
* we could display the ids of some tests selected by time to rune, or cputime,
450
* We could run tests multiple times and report deviation/slowest/fastest.
452
* Gather lsprofile output for each test individually - log that somewhere.
454
* Should plugins be able to offer benchmark tests ?
458
Ensure changeset command behaves properly w/revisions (e.g. 0)
459
Figure out whether testament-related bug is my problem
460
Get rid of the 'old' directory
462
What to do about ghost ancestors in remote branch that are present locally?
added
removed
TODO
