repo init based on the date

[Dan Raaka]

How can I checkout the cupcake branch based on the date ?
for example .. March 27th cupcake branch ..

-Dan

[Shawn Pearce]

You can't by date; repo init doesn't support date based points.

[Dan Raaka]

I looked into using export-manifest, however I get an error

$ repo export-manifest -r -o cupcake_mine.xml
repo: 'export-manifest' is not a repo command. See 'repo help'.

$ repo --version
repo version v1.6.5
(from git://android.git.kernel.org/tools/repo.git)
git version 1.5.6.3
Python 2.5.2 (r252:60911, Oct 5 2008, 19:24:49)
[GCC 4.3.2]

What version of repo supports export-manifest ?

On Apr 19, 5:45 pm, Shawn Pearce <s...@google.com> wrote:
> You can't by date; repo init doesn't support date based points.
>

[Jean-Baptiste Queru]

The command is now actually called repo manifest, not repo export-manifest.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Dan Raaka]

"manifest" did the trick.

what about checkout based on a tag? like v1.6.1 <- I am referring to
OHA repositories
Is there a mapping between those version numbers and dates when they
were created ?

[Jean-Baptiste Queru]

We haven't created many such tags.

For android-sdk-1.5-pre, we have tags "for reference", but the "live"
way to get the source code is to use the android-sdk-1.5-pre manifest
branch (which points to a manifest that directly has the SHA-1 for
each project): see here
http://android.git.kernel.org/?p=platform/manifest.git;a=commit;h=7c733a16553d4748fb869788a248ce0e215b69c1

JBQ

[dan raaka]

From git://android.git.kernel.org/tools/repo          
 * [new tag]         v1.0       -> v1.0               
 * [new tag]         v1.0.1     -> v1.0.1             

 * [new tag]         v1.0.2     -> v1.0.2             
 * [new tag]         v1.0.3     -> v1.0.3             
 * [new tag]         v1.0.4     -> v1.0.4             
 * [new tag]         v1.0.5     -> v1.0.5             

 * [new tag]         v1.0.6     -> v1.0.6             
 * [new tag]         v1.0.7     -> v1.0.7             
 * [new tag]         v1.0.8     -> v1.0.8             
 * [new tag]         v1.0.9     -> v1.0.9             

 * [new tag]         v1.1       -> v1.1               
 * [new tag]         v1.2       -> v1.2               
 * [new tag]         v1.3       -> v1.3               
 * [new tag]         v1.3.1     -> v1.3.1             

 * [new tag]         v1.3.2     -> v1.3.2             
 * [new tag]         v1.4       -> v1.4
 * [new tag]         v1.4.1     -> v1.4.1
 * [new tag]         v1.4.2     -> v1.4.2
 * [new tag]         v1.4.3     -> v1.4.3

 * [new tag]         v1.4.4     -> v1.4.4

I was referring "incorrectly" to above as tags for whole source !!.