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:
204
185
* BZRDIR should be in branch.py not __init__.py.
206
* ``status `` should accept a -r option to show changes relative to a revision,
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.
212
* ~/.bzr.log is not written anymore for some reason.
214
194
* merge should add all revision and inventory XML to the local store.
216
196
* check should give a warning for revisions that are named in the
223
203
just get the id for the selected files, look up their location and
224
204
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.
229
206
* Fix up Inventory objects to represent root object as an entry.
231
208
* Don't convert entire entry from ElementTree to an object when it is
308
285
- Class that describes the state of a working tree so we can just
309
286
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.
318
288
* Try using XSLT to add some formatting to REST-generated HTML. Or
319
289
maybe write a small Python program that specifies a header and foot
320
290
for the pages and calls into the docutils libraries.
337
307
- Hold the ElementTree in memory in the Inventory object and work
338
308
directly on that, rather than converting into Python objects every
339
time it is read in. Probably still exposoe it through some kind of
309
time it is read in. Probably still expose it through some kind of
340
310
object interface though, but perhaps that should just be a proxy
341
311
for the elements.
349
319
* stat cache should perhaps only stat files as necessary, rather than
350
320
doing them all up-front. On the other hand, that disallows the
351
opimization of stating them in inode order.
321
optimization of stating them in inode order.
353
323
* It'd be nice to pipeline multiple HTTP requests. Often we can
354
324
predict what will be wanted in future: all revisions, or all texts
372
340
* XML attributes might have trouble with filenames containing \n and
373
341
\r. Do we really want to support this? I think perhaps not.
375
* Remember execute bits, so that exports will work OK.
377
343
* Unify smart_add and plain Branch.add(); perhaps smart_add should
378
344
just build a list of files to add and pass that to the regular add
381
347
* Function to list a directory, saying in which revision each file was
382
last modified. Useful for web and gui interfaces, and slow to
348
last modified. Useful for web and GUI interfaces, and slow to
383
349
compute one file at a time.
385
351
This will be done when we track file texts by referring to the
390
356
* Perhaps attempts to get locks should timeout after some period of
391
357
time, or at least display a progress message.
393
* Split out upgrade functionality from check command into a separate
396
359
* Don't pass around command classes but rather pass objects. This'd
397
360
make it cleaner to construct objects wrapping external commands.
399
362
* 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
364
* ``uncommit`` command that removes a revision from the end of the
409
365
revision-history; just doing this is enough to remove the commit,
410
366
and a new commit will automatically be made against the
411
367
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
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
374
* ``bzrlib.lazy_import.lazy_import`` could check to see if a given
375
module has already been imported (look at ``sys.modules``). If it
376
has, then just import it directly, rather than creating a lazy
492
443
with removing the tags on the way back in.
450
* Write some benchmark tests
452
* we could display the ids of some tests selected by time to rune, or cputime,
455
* We could run tests multiple times and report deviation/slowest/fastest.
457
* Gather lsprofile output for each test individually - log that somewhere.
459
* Should plugins be able to offer benchmark tests ?
463
Ensure changeset command behaves properly w/revisions (e.g. 0)
464
Figure out whether testament-related bug is my problem
465
Get rid of the 'old' directory
467
What to do about ghost ancestors in remote branch that are present locally?
added
removed
TODO
