[LUDOC-127] can't push changes Created: 07/Mar/13 Updated: 07/Mar/13 Resolved: 07/Mar/13 |
|
| Status: | Closed |
| Project: | Lustre Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Richard Henwood (Inactive) | Assignee: | Joshua Kugler (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 7040 |
| Description |
|
I've tried to push a change, and it doesn't work: $ git push ssh://rhenwood@review.whamcloud.com:29418/doc/manual HEAD:refs/for/master Counting objects: 14, done. Delta compression using up to 8 threads. Compressing objects: 100% (8/8), done. Writing objects: 100% (8/8), 1.41 KiB, done. Total 8 (delta 5), reused 0 (delta 0) remote: Resolving deltas: 0% (0/5) To ssh://rhenwood@review.whamcloud.com:29418/doc/manual ! [remote rejected] HEAD -> refs/for/master (not Signed-off-by author/committer/uploader) error: failed to push some refs to 'ssh://rhenwood@review.whamcloud.com:29418/doc/manual' the commit message looks like this: LUDOC-126 startup: components must be started in the correct order.
This corrects the section in the manual that describes the correct order
for staring Lustre components.
Signed-off-by: Richard Henwood <richard.henwood@intel.com>
|
| Comments |
| Comment by Richard Henwood (Inactive) [ 07/Mar/13 ] |
|
Refreshing my clone fixed this problem. |
| Comment by Andreas Dilger [ 07/Mar/13 ] |
|
Richard, is it possible that there is some patch that isn't from you on the branch you are trying to push? It might be that there is an earlier uncommitted patch from someone else that Gerrit is complaining about? What does "git log" show? The other potential problem is if you are pushing with "richard.henwood@intel.com" but this email is not registered to your account (maybe only your @whamcloud.com address)? |
| Comment by Joshua Kugler (Inactive) [ 07/Mar/13 ] |
|
adilger Richard did confirm he had his @intel.com address in Gerrit. I did not think to ask him to look at his git log. |