'git repo upload' report errors when using latest-ok version about git-repo-go

[jiangxin]

It's not recommend to do like this. Projects with fixed revisions in a manifest.xml should not been changed. If you really want to so, we may:

1. Define two revision for project in a manifest file. One revision is a fixed revision which is used for checking out the worktree, and another revision should point to a branch which used for user to upload changes.
2. The worktree will never get chance to be updated, because of the fixed revision. Any changes synced from upstream in local worktree will be treated as changes need to be uploaded to upstream.

Is that what you want?

[guestliu]

It's not recommend to do like this. Projects with fixed revisions in a manifest.xml should not been changed. If you really want to so, we may:

1. Define two revision for project in a manifest file. One revision is a fixed revision which is used for checking out the worktree, and another revision should point to a branch which used for user to upload changes.
2. The worktree will never get chance to be updated, because of the fixed revision. Any changes synced from upstream in local worktree will be treated as changes need to be uploaded to upstream.

Is that what you want?

1. Why 'git pr' works but 'git repo upload' fails?
2. 'Define two revisions' does not make sense, one revision is the fixed revision and the next one is the newest revision on the branch which is always in change.
3. 'The worktree will never get chance to be updated' is FALSE. The manifest file(latest_ok_release.xml) may be changed in the remote. When we run 'git repo sync' , we will sync a newest latest-ok version whose revisions are fixed.