Brian Harring 14a6674e32 manifest: record the original revision when in -r mode.
Currently when doing a sync against a revision locked manifest,
sync has no option but to fall back to sync'ing the entire refs space;
it doesn't know which ref to ask for that contains the sha1 it wants.

This sucks if we're in -c mode; thus when we generate a revision
locked manifest, record the originating branch- and try syncing that
branch first.  If the sha1 is found within that branch, this saves
us having to pull down the rest of the repo- a potentially heavy
saving.

If that branch doesn't have the desired sha1, we fallback to sync'ing
everything.

Change-Id: I99a5e44fa1d792dfcada76956a2363187df94cf1
2012-09-28 22:31:27 -07:00
2009-06-02 00:09:07 +02:00
2009-06-02 00:09:07 +02:00
2012-08-23 12:15:26 +02:00
2008-10-21 07:00:00 -07:00
2012-04-13 09:46:00 -07:00
2012-08-23 12:15:26 +02:00
2012-08-23 12:15:26 +02:00
2011-09-19 14:52:57 -07:00
Description
No description provided
Apache-2.0 35 MiB
Languages
Python 99.1%
Shell 0.9%