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