1 Commands still missing completely;
2 replace Replace a token with a new value for that token.
3 resolve Mark any conflicts to the working copy for manual resolution.
4 tag Tag the contents of the repository with a version name.
5 setpref Set a value for a preference (test, predist, ...).
6 rollback Record an inverse patch without changing the working directory.
7 diff Create a diff between two versions of the repository.
8 annotate Display which patch last modified something.
9 trackdown Locate the most recent version lacking an error.
10 query Query information which is stored by vng.
11 pull Copy and apply patches from another repository to this one.
12 unpull Opposite of pull; unsafe if patch is not in remote repository.
13 obliterate Delete selected patches from the repository. (UNSAFE!)
14 send Send by email a bundle of one or more patches.
15 apply Apply patches (from an email bundle) to the repository.
16 get Create a local copy of another repository.
17 put Makes a copy of the repository
18 optimize Optimize the repository.
19 check Check the repository for consistency.
20 repair Repair the corrupted repository.
26 * cursor help (when typing '?') seems to be hardcoded to 'revert'.
27 * test each command to honor its arguments and options.
28 * Use pager for help :)
29 * Use $PAGER for pager
30 * For a record -a let no more than, say, 30 seconds pass before just popping up the
31 editor without all of the hunks fetched.
32 * Make the --debug option only available when compiling as debug-build
35 * Also show / store file permissions in the diff and thus in revert
36 * After a revert, and the file ends up with no changes, we should do an update-index on it.
38 use git-read-tree --reset HEAD and git-update-index --refresh to implement 'check'
39 use 'prune' and 'pack' to implement optimize.
42 git ls-remote -h -t [remote] to fetch all branches.
43 allow the user to select the branches he wants to mirror.
47 [09:31] <brad> git people: is it possible to push just a single commit to devil, or does it ineed to be a branch?
48 [09:31] <simon> brad: you can for example do: git push <remote> <sha1>:name-of-new-branch
49 [09:31] <simon> brad: and later remove the branch again with git push <remote> :name-of-new-branch
50 [09:31] <brad> ahh, cool
53 http://wiki.winehq.org/GitWine