1
* add --all-files to `stdhome st` to show status of all files in repo? or
2
should we add `stdhome ls`?
3
* 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? It means ~/src (which is
5
a symlink in my home repo) shows as modified when compared to the symlink of
7
* add ~/bin/rebuild-tags!
8
* look at what need to be done before v0.1
9
* make the copy walker accept symlinks in place of files (as well as
10
directories) if they are on the symlink accept list
11
* check that bin/quicktile.py on tims-laptop is an acceptable symlink
13
* check directory permissions before updating them
14
* during copy-out (not copy-in), show what is being changed with lines like
15
"<SP><SP><OP><SP><FILE>" where OP is A (add), D (delete), M (modified) and K
17
* currently, verbose print lines for bzr stuff are in the commands -- should
18
they be in the bzr module?
19
* make the copy walker accept symlinks that differ if they are on the symlink
20
accept list (so that symlinks can be pointed elsewhere in ~/)
21
* add code that can determine a relative file from a full file and a basepoint
22
* when ignoring files in the walker, populate the list of file more
23
inteligently. ".bzr" (and ".bzrignore") need to come from the VCS backend.
24
".stdhome", ".stdhomerc" and/or ".stdhomeignore" need to be converted to full
25
filenames and then their relative file names derived from the configured home
27
* KNOWN ISSUE: handle renames as renames (rather than delete + add) because a
28
directory renamed in the repo could contain other stuff that isn't versioned
29
in ~/ which is lost, at the moment
30
* KNOWN ISSUE: decide on whether to implement remote --keep flag (see plan:483);
31
currently, on the remote end, stuff deleted in repo during an update deletes