Tag feature to allow named and reproducible versions of the global code base to be defined about git-repo

[GoogleCodeExporter]

Comment by Shawn Pearce <[email protected]> on Mon Feb 09 10:28:26 PST 2009

On a related note, I received this request by email from another user:
--------

So, I believe I'd like to see something like

repo sync [branch]@Sha1

Expected Behavior:
- Syncs each repository to the state it was before sha1 was checked in.
- Sha1 pretty much only indicates the time of checkin. So, each repository is
synced to the state at that time.
- It would be really nice to get repo sync to write a meta-data file that
would indicate what sha1s were the latest for each repository
- I am not sure how the branch option would fit in but we are pretty much just
syncing the branch at that given time the sha1 was checked in.

Original comment by [email protected] on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Comment by Shawn Pearce <[email protected]> on Tue Mar 03 18:04:39 PST 2009

https://review.source.android.com/9051 is perhaps part of the solution, by
providing a manifest export that contains pegged revisions.

Original comment by [email protected] on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Comment by Patrick Brady <[email protected]> on Wed Apr 29 09:10:20 PDT 2009

It would be great to have:

repo sync --tag <tag>

execute:

repo forall -c "git checkout <tag>"

so you could repo init once to a single branch, and then easily sync between
snapshots.

Original comment by [email protected] on 24 Sep 2009 at 9:11

[GoogleCodeExporter]

Original comment by [email protected] on 24 Sep 2009 at 11:12

[GoogleCodeExporter]

Yeah, repo tag would definitely be great. Or maybe I'm missing another way to 
do the equivalent.

Original comment by [email protected] on 26 Jul 2011 at 9:10

[GoogleCodeExporter]

I figured it out. If your have a tag in a manifest file (version.xml for 
example). You can repo init to a specific tag with the following command:

repo init -u <addres> -b refs/tags/<tagname> -m version.xml

Original comment by [email protected] on 28 Oct 2013 at 2:04