Hi all
My issue has been resolved by using "git rebase --onto ". Thanks for your
reply.
Regards
zhengguang
2014-04-19 23:50 GMT-04:00 Chris Behrens :
> Ya, there's 2 commits in your branch. If you want to push them both up,
> it'll create 2 separate reviews with a dependency chain. Just answe
Ya, there's 2 commits in your branch. If you want to push them both up, it'll
create 2 separate reviews with a dependency chain. Just answer 'yes' to the
question.
If you meant to push them up separately without a dependency chain, put both
commits in separate branches and then git review them
You have to do create a branch in the form:
git checkout -b bug/#bugnumber
Then do your commit, if you failed ot asked to do other stuff in yoir
previous commit do the changes in the same branch do commit like:
git add file
git commit --amend
git review
El abr 19, 2014 10:09 PM, "Zhengguang Ou"
Zhengguang Ou wrote on 04/19/2014 11:01:19 PM:
> Hi all
> I used the "git review" to submit a commit, but I got a error as follow:
> You have more than one commit that you are about to submit.
> The outstanding commits are:
> 5dc6eeb (HEAD, Bug1309986) Add unit test for keypair's api
> d10e307 (r
Hi all
I used the "git review" to submit a commit, but I got a error as follow:
You have more than one commit that you are about to submit.
The outstanding commits are:
5dc6eeb (HEAD, Bug1309986) Add unit test for keypair's api
d10e307 (review/zhengguang_ou/Bug1307338) Fix the incorrect return m
