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
20
27
* Fix tests so that import errors caused by modules don't produce false reports
21
28
that the tests themselves don't exist.
53
60
* -r option should take a revision-id as well as a revno.
62
* allow ``bzr st -r 300`` to show a summary of changes since then.
55
64
* ``bzr info`` should count only people with distinct email addresses as
56
65
different committers. (Or perhaps only distinct userids?)
82
91
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
83
92
giving options to display ids, types, etc.
94
* Split BzrError into various more specific subclasses for different
95
errors people might want to catch.
97
* If the export destination ends in '.tar', '.tar.gz', etc then create
98
a tarball instead of a directory. (Need to actually make a
99
temporary directory and then tar that up.)
101
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
85
103
* RemoteBranch could maintain a cache either in memory or on disk. We
86
104
know more than an external cache might about which files are
87
105
immutable and which can vary. On the other hand, it's much simpler
127
145
methods return object, but what we really want is the raw XML, which
128
146
can be popped into our own store. That needs to be refactored.
148
* ``bzr status FOO`` where foo is ignored should say so.
150
* ``bzr mkdir A...`` should just create and add A.
130
152
* Guard against repeatedly merging any particular patch.
132
154
* More options for diff:
185
209
* 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.
211
* ``status `` should accept a -r option to show changes relative to a revision,
217
* ~/.bzr.log is not written anymore for some reason.
194
219
* merge should add all revision and inventory XML to the local store.
196
221
* check should give a warning for revisions that are named in the
203
228
just get the id for the selected files, look up their location and
204
229
diff just those files. No need to traverse the entire inventories.
231
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
232
under that directory.
206
234
* Fix up Inventory objects to represent root object as an entry.
208
236
* Don't convert entire entry from ElementTree to an object when it is
285
313
- Class that describes the state of a working tree so we can just
286
314
assert it's equal.
316
* There are too many methods on Branch() that really manipulate the
317
WorkingTree. They should be moved across.
319
Also there are some methods which are duplicated on Tree and
320
Inventory objects, and it should be made more clear which ones are
321
proxies and which ones behave differently, and how.
288
323
* Try using XSLT to add some formatting to REST-generated HTML. Or
289
324
maybe write a small Python program that specifies a header and foot
290
325
for the pages and calls into the docutils libraries.
307
342
- Hold the ElementTree in memory in the Inventory object and work
308
343
directly on that, rather than converting into Python objects every
309
time it is read in. Probably still expose it through some kind of
344
time it is read in. Probably still exposoe it through some kind of
310
345
object interface though, but perhaps that should just be a proxy
311
346
for the elements.
319
354
* stat cache should perhaps only stat files as necessary, rather than
320
355
doing them all up-front. On the other hand, that disallows the
321
optimization of stating them in inode order.
356
opimization of stating them in inode order.
323
358
* It'd be nice to pipeline multiple HTTP requests. Often we can
324
359
predict what will be wanted in future: all revisions, or all texts
340
377
* XML attributes might have trouble with filenames containing \n and
341
378
\r. Do we really want to support this? I think perhaps not.
380
* Remember execute bits, so that exports will work OK.
343
382
* Unify smart_add and plain Branch.add(); perhaps smart_add should
344
383
just build a list of files to add and pass that to the regular add
347
386
* Function to list a directory, saying in which revision each file was
348
last modified. Useful for web and GUI interfaces, and slow to
387
last modified. Useful for web and gui interfaces, and slow to
349
388
compute one file at a time.
351
390
This will be done when we track file texts by referring to the
356
395
* Perhaps attempts to get locks should timeout after some period of
357
396
time, or at least display a progress message.
398
* Split out upgrade functionality from check command into a separate
359
401
* Don't pass around command classes but rather pass objects. This'd
360
402
make it cleaner to construct objects wrapping external commands.
362
404
* Track all merged-in revisions in a versioned add-only metafile.
406
* ``pull --clobber`` should discard any local changes not present
407
remotely. Not generally what you want, but possibly useful when
408
you're just mirroring another branch and want to keep tracking it
409
even when they e.g. uncommit or make similar non-forward movements.
410
Also for push I suppose. Clobber may not be the best name, maybe
364
413
* ``uncommit`` command that removes a revision from the end of the
365
414
revision-history; just doing this is enough to remove the commit,
366
415
and a new commit will automatically be made against the
367
416
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
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
418
It only makes sense to delete from the tail of history, not from the
421
The revision, its inventory and texts remain floating in the store.
422
We should perhaps add the revision to a list of removed-commits, so
423
that it can be restored or at least accounted for when checking
424
consistency. This file would not be versioned, and probably should
425
not propagate when branched.
427
If we track merged revisions then we need to update this list too.
428
If the list is stored in a weave it's easy (implicit): the version
429
of the list can remain but it won't be referenced anymore. It's
430
probably best to just store this list in a weave in the first place
443
497
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
