1 Commands still missing completely;
2 replace Replace a token with a new value for that token.
3 amend-record Replace a patch with a better version before it leaves your repository.
4 resolve Mark any conflicts to the working copy for manual resolution.
5 tag Tag the contents of the repository with a version name.
6 setpref Set a value for a preference (test, predist, ...).
7 rollback Record an inverse patch without changing the working directory.
8 diff Create a diff between two versions of the repository.
9 annotate Display which patch last modified something.
10 trackdown Locate the most recent version lacking an error.
11 query Query information which is stored by vng.
12 pull Copy and apply patches from another repository to this one.
13 unpull Opposite of pull; unsafe if patch is not in remote repository.
14 obliterate Delete selected patches from the repository. (UNSAFE!)
15 send Send by email a bundle of one or more patches.
16 apply Apply patches (from an email bundle) to the repository.
17 get Create a local copy of another repository.
18 put Makes a copy of the repository
19 optimize Optimize the repository.
20 check Check the repository for consistency.
21 repair Repair the corrupted repository.
27 * cursor help (when typing '?') seems to be hardcoded to 'revert'.
28 * test each command to honor its arguments and options.
29 * Use pager for help :)
30 * Use $PAGER for pager
31 * if passing -a and -m to record, just get the changed files not the diffs.
32 * For a record -a let no more than, say, 30 seconds pass before just popping up the
33 editor without all of the hunks fetched.
34 * Make the --debug option only available when compiling as debug-build
37 * record on a non-clear repo (where some things have been added or an added file has been removed from FS)
39 * Getting a diff in another thread where all files are actually not changed should result in an empty
41 * Also show / store file permissions in the diff and thus in revert
42 * Instead of hardcoding '.git' as a dirname; use git-rev-parse in Configuration and in commits/Commit
43 Maybe we should just use $GIT_DIR ?
44 * After a revert, and the file ends up with no changes, we should do an update-index on it.
45 * changes does not detect renames
46 * On a big windows repo fetching initial diff may timeout. :(
47 * make the revert cursor have its count updated when the diff is done.
48 * record; check for empty commit message. Also remove leading and trailing linefeeds.
50 use git-read-tree --reset HEAD and git-update-index --refresh to implement 'check'
51 use 'prune' and 'pack' to implement optimize.
54 git ls-remote -h -t [remote] to fetch all branches.
55 allow the user to select the branches he wants to mirror.
59 [09:31] <brad> git people: is it possible to push just a single commit to devil, or does it ineed to be a branch?
60 [09:31] <simon> brad: you can for example do: git push <remote> <sha1>:name-of-new-branch
61 [09:31] <simon> brad: and later remove the branch again with git push <remote> :name-of-new-branch
62 [09:31] <brad> ahh, cool
65 git checkout -b tmp HEAD~5 # rewind to the commit in question
66 vi file.c # edit the file
67 git commit --amend file.c # redo the commit without deleting the commit
68 git rebase --onto tmp master~5 master # replay the later changes
69 git branch -D tmp # clean up the temporary branch
71 Where there are a number of files to amend you are probably better off using:
72 git checkout -b tmp HEAD~5 # rewind to the commit in question
73 git reset HEAD^ # delete the commit at the now current point
75 vi file2.c # the files
76 git commit -a -c ORIG_HEAD # redo the commit incorporating all changed files
77 git rebase --onto tmp master~5 master # replay the later changes
78 git branch -D tmp # clean up the temporary branch
81 http://wiki.winehq.org/GitWine