1 Commands still missing completely;
2 resolve Mark any conflicts to the working copy for manual resolution.
3 tag Tag the contents of the repository with a version name.
4 setpref Set a value for a preference (test, predist, ...).
5 rollback Record an inverse patch without changing the working directory.
6 annotate Display which patch last modified something.
7 trackdown Locate the most recent version lacking an error.
8 query Query information which is stored by vng.
9 unpull Opposite of pull; unsafe if patch is not in remote repository.
10 obliterate Delete selected patches from the repository. (UNSAFE!)
11 send Send by email a bundle of one or more patches.
12 apply Apply patches (from an email bundle) to the repository.
13 get Create a local copy of another repository.
14 put Makes a copy of the repository
15 optimize Optimize the repository.
16 check Check the repository for consistency.
17 repair Repair the corrupted repository.
23 * cursor help (when typing '?') seems to be hardcoded to 'revert'.
24 * test each command to honor its arguments and options.
25 * Use pager for help :)
26 * Use $PAGER for pager
27 * For a record -a let no more than, say, 30 seconds pass before just popping up the
28 editor without all of the hunks fetched.
29 * Make the --debug option only available when compiling as debug-build
32 unrevert doesn't work for file renames/adds
33 Pressing enter on single char input (end of 'revert') should ask again
35 use git-read-tree --reset HEAD and git-update-index --refresh to implement 'check'
36 use 'prune' and 'pack' to implement optimize.
38 [09:31] <brad> git people: is it possible to push just a single commit to devil, or does it ineed to be a branch?
39 [09:31] <simon> brad: you can for example do: git push <remote> <sha1>:name-of-new-branch
40 [09:31] <simon> brad: and later remove the branch again with git push <remote> :name-of-new-branch
41 [09:31] <brad> ahh, cool
44 http://wiki.winehq.org/GitWine