1
* perform update with conflict
3
* performing an "add", when the repo is not up-to-date (i.e., there are updates
4
pending) just prints "stdhome add: bzr commit", with no other explaination as
7
1
* add --all-files to `stdhome st` to show status of all files in repo? or
8
2
should we add `stdhome ls`?
10
3
* symlink substitutes don't acept a symlink in the repo and a directory on the
11
4
FS (as well as the other way around). Should they? It means ~/src (which is
12
5
a symlink in my home repo) shows as modified when compared to the symlink of
13
6
the same name on oak.
15
7
* skip unchanged directories
16
8
now that update, revert, resolve and init report on home dir changes, resolve
17
9
and revert show all directories as being modified (because we always copy
18
10
them out without checking for changes)
20
11
* add ~/bin/rebuild-tags!
22
12
* look at what need to be done before v0.1
24
13
* make the copy walker accept symlinks in place of files (as well as
25
14
directories) if they are on the symlink accept list
27
15
* check that bin/quicktile.py on tims-laptop is an acceptable symlink
31
17
* check directory permissions before updating them
33
18
* during copy-out (not copy-in), show what is being changed with lines like
34
19
"<SP><SP><OP><SP><FILE>" where OP is A (add), D (delete), M (modified) and K
37
21
* currently, verbose print lines for bzr stuff are in the commands -- should
38
22
they be in the bzr module?
40
23
* make the copy walker accept symlinks that differ if they are on the symlink
41
24
accept list (so that symlinks can be pointed elsewhere in ~/)
43
25
* add code that can determine a relative file from a full file and a basepoint
45
26
* when ignoring files in the walker, populate the list of file more
46
27
inteligently. ".bzr" (and ".bzrignore") need to come from the VCS backend.
47
28
".stdhome", ".stdhomerc" and/or ".stdhomeignore" need to be converted to full
48
29
filenames and then their relative file names derived from the configured home
51
31
* KNOWN ISSUE: handle renames as renames (rather than delete + add) because a
52
32
directory renamed in the repo could contain other stuff that isn't versioned
53
33
in ~/ which is lost, at the moment
55
34
* KNOWN ISSUE: decide on whether to implement remote --keep flag (see plan:483);
56
35
currently, on the remote end, stuff deleted in repo during an update deletes
added
removed
tools/todo.org
