From a58f2ec4041dafafc492e377e8a7ac9f5ef7d357 Mon Sep 17 00:00:00 2001 From: "http://scs11.myopenid.com/" Date: Wed, 8 Sep 2010 10:34:17 -0700 Subject: [PATCH] --- AFSLore/GitDevelopers.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/AFSLore/GitDevelopers.mdwn b/AFSLore/GitDevelopers.mdwn index af17727..d4ae0dd 100644 --- a/AFSLore/GitDevelopers.mdwn +++ b/AFSLore/GitDevelopers.mdwn @@ -235,8 +235,8 @@ Assuming all has gone well, this will have added the entry to the code review qu It's possible that your modifications won't be accepted first time. In this case, you need to revise your changes, and resubmit them to gerrit. Please note that this should always be done by modifying your original changeset, _not_ by submitting a new change that makes the required fixes. Either git commit --amend, or git rebase should be used to combine your changes with the original changeset, and then you should push this to gerrit with git push ssh://gerrit.openafs.org/openafs.git :refs/changes/ - -(where <hash> is the sha1 hash of the revised change, and <number> is the change number you received when you originally submitted the patch) + +(where <hash> is the sha1 hash of the revised change that follows the word commit in the log message, and <number> is the change number you received when you originally submitted the patch) You can obtain the sha1 hash of a commit by using 'git show' (if it is on the tip of your current branch), or 'git log' (if it is in your history) -- 1.9.4