improvements to the way we sync to a particular build

[GoogleCodeExporter]

Reported by Andrew D. Stadler (Google) <stadler@android.com> on Fri Jun 12 
15:07:05 PDT 2009
Source: JIRA REPO-38

This is a feature request that I will actually try hacking myself, but filing
the FR so it can be tracked, commented on, etc.

The current workflow:
  1. get manifest
  2. copy to special location
  3. repo init -m manifest-name
  4. repo sync
  5. to return to "latest", repo init -m default.xml

Is a heck of a lot more steps than our old friend p4 sync //branches/...@CL#

I propose the following changes that can be taken in parts or together to
improve the process at each step.

* The argument should be a simple filename.  This has a dual benefit:  1.
allows you to download the manifest anywhere 2. you can type the command using
completion instead of a full retype.  The code could simply pick up the file
and copy it into the correct directory, and then proceed using the existing
init code.

* Any time we repo sync and the manifest is not default.xml, print a warning.
This helps with the "why am I not getting anything" confusion, when you forgot
that you did this earlier.

* Add -m to repo sync and insert "repo init -m" step if found.  This turns two
commands into one.

* For extra credit, convert build # into URL and download the manifest
automatically

Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Original comment by sop+code@google.com on 24 Sep 2009 at 11:08

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Moot with issue 49 (atomic sync).

Original comment by sop+code@google.com on 24 Sep 2009 at 11:20

• Changed state: WontFix
• Added labels: ****
• Removed labels: ****