81
83
http://www.gelato.unsw.edu.au/archives/git/0504/2194.html
85
* testbzr should by default test the bzr binary in the same directory
86
as the testbzr script, or take a path to it as a first parameter.
88
Should show the version from bzr and the path name.
83
90
* RemoteBranch could maintain a cache either in memory or on disk. We
84
91
know more than an external cache might about which files are
85
92
immutable and which can vary. On the other hand, it's much simpler
86
93
to just use an external proxy cache.
88
Perhaps ~/.bzr/http-cache. Baz has a fairly simple cache under
89
~/.arch-cache, containing revision information encoded almost as a
90
bunch of archives. Perhaps we could simply store full paths.
92
* Maybe also store directories in the statcache so that we can quickly
93
identify that they still exist.
95
* Diff should show timestamps; for files from the working directory we
96
can use the file itself; for files from a revision we should use the
97
commit time of the revision.
99
* Perhaps split command infrastructure from the actual command
102
* Cleaner support for negative boolean options like --no-recurse.
104
* Statcache should possibly map all file paths to / separators
106
* quotefn doubles all backslashes on Windows; this is probably not the
107
best thing to do. What would be a better way to safely represent
108
filenames? Perhaps we could doublequote things containing spaces,
109
on the principle that filenames containing quotes are unlikely?
110
Nice for humans; less good for machine parsing.
112
* Patches should probably use only forward slashes, even on Windows,
113
otherwise Unix patch can't apply them. (?)
115
* Branch.update_revisions() inefficiently fetches revisions from the
116
remote server twice; once to find out what text and inventory they
117
need and then again to actually get the thing. This is a bit
120
One complicating factor here is that we don't really want to have
121
revisions present in the revision-store until all their constituent
122
parts are also stored.
124
The basic problem is that RemoteBranch.get_revision() and similar
125
methods return object, but what we really want is the raw XML, which
126
can be popped into our own store. That needs to be refactored.
128
* ``bzr status FOO`` where foo is ignored should say so.
99
* Change command functions into Command() objects, like in hct, and
100
then the grammar can be described directly in there. Since all
101
option definitions are global we can define them just once and
102
reference them from each command.
104
* Selective commit of only some files.
106
* Faster diff/status.
108
Status should be handled differently because it needs to report on
109
deleted and unknown files. diff only needs to deal with versioned
112
* Merge Aaron's merge code.
135
114
* Merge revert patch.
137
116
* ``bzr mv`` that does either rename or move as in Unix.
139
* More efficient diff of only selected files. We should be able to
140
just get the id for the selected files, look up their location and
141
diff just those files. No need to traverse the entire inventories.
143
* ``bzr status DIR`` or ``bzr diff DIR`` should report on all changes
144
under that directory.
118
* More efficient diff of only selected files.
146
120
* Fix up Inventory objects to represent root object as an entry.
148
* Don't convert entire entry from ElementTree to an object when it is
149
read in, but rather wait until the program actually wants to know
122
* Don't convert entire entry from
152
124
* Extract changes from one revision to the next to a text form
153
125
suitable for transmission over email.
155
127
* More test cases.
157
- Selected-file commit
159
- Impossible selected-file commit: adding things in non-versioned
160
directories, crossing renames, etc.
162
129
* Write a reproducible benchmark, perhaps importing various kernel versions.
131
* Change test.sh from Bourne shell into something in pure Python so
132
that it can be more portable.
164
134
* Directly import diffs! It seems a bit redundant to need to rescan
165
135
the directory to work out what files diff added/deleted/changed when
166
136
all the information is there in the diff in the first place.
276
246
urlgrabber's docs say they are working on batched downloads; we
277
247
could perhaps ride on that or just create a background thread (ew).
249
* Should be a signature at the top of the cache file.
279
251
* Paranoid mode where we never trust SHA-1 matches.
281
* Don't commit if there are no changes unless forced.
283
* --dry-run mode for commit? (Or maybe just run with
284
check-command=false?)
286
* Generally, be a bit more verbose unless --silent is specified.
288
* Function that finds all changes to files under a given directory;
289
perhaps log should use this if a directory is given.
291
* XML attributes might have trouble with filenames containing \n and
292
\r. Do we really want to support this? I think perhaps not.
294
* Remember execute bits, so that exports will work OK.
296
* Unify smart_add and plain Branch.add(); perhaps smart_add should
297
just build a list of files to add and pass that to the regular add
300
* Function to list a directory, saying in which revision each file was
301
last modified. Useful for web and gui interfaces, and slow to
302
compute one file at a time.
304
* unittest is standard, but the results are kind of ugly; would be
305
nice to make it cleaner.
307
* Check locking is correct during merge-related operations.
309
* Perhaps attempts to get locks should timeout after some period of
310
time, or at least display a progress message.
312
* Split out upgrade functionality from check command into a separate
347
285
files, and respecting selective commits. Run the pre-commit check
348
286
(e.g. compile and run test suite) in there.
350
Possibly this should be done by splitting the commit function into
351
several parts (under a single interface). It is already rather
352
large. Decomposition:
354
- find tree modifications and prepare in-memory inventory
356
- export that inventory to a temporary directory
358
- run the test in that temporary directory
360
- if that succeeded, continue to actually finish the commit
362
What should be done with the text of modified files while this is
363
underway? I don't think we want to count on holding them in memory
364
and we can't trust the working files to stay in one place so I
365
suppose we need to move them into the text store, or otherwise into
366
a temporary directory.
368
If the commit does not actually complete, we would rather the
369
content was not left behind in the stores.
373
290
* GUI (maybe in Python GTK+?)
added
removed
TODO
