Affected Version: repo version v1.7.3.1
Environment: Ubuntu 10.04 x86_64
git version 1.7.0.4
Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41)
[GCC 4.4.3]
Repo 'upload' and 'manifest' commands at least are unaware of any topic
branches created in a specific git repository via 'git checkout -b <branch>'
command instead of 'repo start' command.
What steps will reproduce the problem?
1. cd <project>
2. git checkout -b newtopic
3. (make changes, git commit -a)
4. repo upload (repo sees no changes)
In case of 'manifest' command, if a branch is created to track different remote
than originally initialized for, 'repo manifest -o <name>.xml' doesn't notice
this.
This is especially confusing because 'repo branch' command does notice branches
created with git commands.
Workaround:
- Always use 'repo start' to create a topic branch
- To switch a specific repo to track a different remote, edit active manifest
and run 'repo sync' for the specified project
Original issue reported on code.google.com by ora...@gmail.com on 1 Mar 2011 at 1:09
Original issue reported on code.google.com by
ora...@gmail.com
on 1 Mar 2011 at 1:09