Reported by Dave Bort <dbort@android.com> on Mon Feb 09 10:36:52 PST 2009
Source: JIRA REPO-4
I've got a commit [in the repo development repository], and git diff m/
default.. shows the deltas I'm expecting, but "repo upload" just gives me "no
branches ready for upload".
$ git branch
* master
--
I'll bet its because .git/config doesn't have any remote or merge entries
listed for the branch, because you didn't create it with --track.
Make a new branch and merge your master branch into it:
$ git branch --track for-upload m/default
$ git checkout for-upload
$ git merge master
$ repo upload
This is why we have repo start (more or less), its shorter than git branch --
track.
--
Repo should provide a way to make a branch "ready for upload", and the "no
branches ready for upload" message should tell the user how to use the new
feature to recover from that state.
--
I was thinking that
repo start <branch> <sha1>
could do the repo start, and then the git reset --hard <sha1>.
It might also be nice to have a -p option (or some other way) of having it do
that on just one project.
Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:09
Original issue reported on code.google.com by
code-rev...@gtempaccount.com
on 24 Sep 2009 at 9:09