1
* perform update with conflict
2
* performing an "add", when the repo is not up-to-date (i.e., there are updates
3
pending) just prints "stdhome add: bzr commit", with no other explaination as
1
5
* add --all-files to `stdhome st` to show status of all files in repo? or
2
should we add `stdhome ls`? I'm favouring ls right now...
6
should we add `stdhome ls`?
3
7
* symlink substitutes don't acept a symlink in the repo and a directory on the
4
FS (as well as the other way around). Should they? I can't think of a use
5
case for this... Note: if this is changed, also update the StatusWalker
6
(used by status and diff commands)
8
FS (as well as the other way around). Should they? It means ~/src (which is
9
a symlink in my home repo) shows as modified when compared to the symlink of
11
* skip unchanged directories
12
now that update, revert, resolve and init report on home dir changes, resolve
13
and revert show all directories as being modified (because we always copy
14
them out without checking for changes)
7
15
* add ~/bin/rebuild-tags!
16
* look at what need to be done before v0.1
8
17
* make the copy walker accept symlinks in place of files (as well as
9
18
directories) if they are on the symlink accept list
10
* look at what need to be done before v0.1
19
* check that bin/quicktile.py on tims-laptop is an acceptable symlink
12
21
* check directory permissions before updating them
13
22
* during copy-out (not copy-in), show what is being changed with lines like
added
removed
tools/todo.org
