diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-11-18 17:17:16 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-11-18 17:19:11 +0000 |
commit | 2354250a95eab484459f41f8715ae112295c2174 (patch) | |
tree | be3af4936a8aa43d6afcd97bc95a7d4448146a14 /bitbake/lib/prserv/serv.py | |
parent | e45d7355f1b0d3336f92683add5753fda54579de (diff) | |
download | poky-2354250a95eab484459f41f8715ae112295c2174.tar.gz |
bitbake: git: Use merge-base instead of log for testing if a commit is present
The current use of git log to check if a given revision is present can be
a little fragile.
For example if revision X was on branch A, and then later added to branch
B, the update checks would not notice this since they just check for X
being in the repository.
We also had some autobuilder corruption where an older packed-refs file
was copied over a new repository containing newer pack files. There
was no update to the refs file since the revision was present but
not accessible in any branch.
The correct fix is to check that the required revisions are present
on the specific branches. This patch does this using merge-base.
(Bitbake rev: 89abfbc1953e3711d6c90aff793ee622c22609b1)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/prserv/serv.py')
0 files changed, 0 insertions, 0 deletions