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