| commit | 336f7bd0ed70f5ee2595463b6bd8dd277e90c833 | [log] [tgz] |
|---|---|---|
| author | Shawn O. Pearce <sop@google.com> | Sat Apr 18 10:39:28 2009 -0700 |
| committer | Shawn O. Pearce <sop@google.com> | Sat Apr 18 10:39:28 2009 -0700 |
| tree | 4854b1808bcda18221e097a69c993c4a0cf6137a | |
| parent | 2810cbc7784e9a21e7001c31b65af94fd9ba7a5b [diff] |
Avoid git fork on the common case of repo not changing Usually repo is upgraded only once a week, if that often. Most of the time we invoke HasChanges on the repo project (or even on the manifest project) the current HEAD will resolve to the same SHA-1 as the remote tracking ref, and there are therefore no changes. Signed-off-by: Shawn O. Pearce <sop@google.com>