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
20
* Fix tests so that import errors caused by modules don't produce false reports
28
21
that the tests themselves don't exist.
60
53
* -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.
64
55
* ``bzr info`` should count only people with distinct email addresses as
65
56
different committers. (Or perhaps only distinct userids?)
91
82
* ``bzr inventory -r REV`` and perhaps unify this with ``bzr ls``,
92
83
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
103
85
* RemoteBranch could maintain a cache either in memory or on disk. We
104
86
know more than an external cache might about which files are
105
87
immutable and which can vary. On the other hand, it's much simpler
145
127
methods return object, but what we really want is the raw XML, which
146
128
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.
152
130
* Guard against repeatedly merging any particular patch.
154
132
* More options for diff:
209
185
* BZRDIR should be in branch.py not __init__.py.
211
* ``status `` should accept a -r option to show changes relative to a revision,
217
* ~/.bzr.log is not written anymore for some reason.
219
190
* merge should add all revision and inventory XML to the local store.
221
192
* check should give a warning for revisions that are named in the
228
199
just get the id for the selected files, look up their location and
229
200
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.
234
202
* Fix up Inventory objects to represent root object as an entry.
236
204
* Don't convert entire entry from ElementTree to an object when it is
313
281
- Class that describes the state of a working tree so we can just
314
282
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.
323
284
* Try using XSLT to add some formatting to REST-generated HTML. Or
324
285
maybe write a small Python program that specifies a header and foot
325
286
for the pages and calls into the docutils libraries.
342
303
- Hold the ElementTree in memory in the Inventory object and work
343
304
directly on that, rather than converting into Python objects every
344
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
345
306
object interface though, but perhaps that should just be a proxy
346
307
for the elements.
354
315
* stat cache should perhaps only stat files as necessary, rather than
355
316
doing them all up-front. On the other hand, that disallows the
356
opimization of stating them in inode order.
317
optimization of stating them in inode order.
358
319
* It'd be nice to pipeline multiple HTTP requests. Often we can
359
320
predict what will be wanted in future: all revisions, or all texts
377
336
* XML attributes might have trouble with filenames containing \n and
378
337
\r. Do we really want to support this? I think perhaps not.
380
* Remember execute bits, so that exports will work OK.
382
339
* Unify smart_add and plain Branch.add(); perhaps smart_add should
383
340
just build a list of files to add and pass that to the regular add
386
343
* Function to list a directory, saying in which revision each file was
387
last modified. Useful for web and gui interfaces, and slow to
344
last modified. Useful for web and GUI interfaces, and slow to
388
345
compute one file at a time.
390
347
This will be done when we track file texts by referring to the
395
352
* Perhaps attempts to get locks should timeout after some period of
396
353
time, or at least display a progress message.
398
* Split out upgrade functionality from check command into a separate
401
355
* Don't pass around command classes but rather pass objects. This'd
402
356
make it cleaner to construct objects wrapping external commands.
404
358
* 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
413
360
* ``uncommit`` command that removes a revision from the end of the
414
361
revision-history; just doing this is enough to remove the commit,
415
362
and a new commit will automatically be made against the
416
363
predecessor. This can be repeated.
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
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
