| commit | 5af858fe95b926f84c5b00751bce00de900f56aa | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Wed, 5 Apr 2017 20:38:49 +0000 (5 13:38 -0700) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Wed, 5 Apr 2017 20:38:49 +0000 (5 13:38 -0700) | ||
| tree | c07c10202f866aea1a3e7440b43bd5c2fc231ecc | treesnapshot (tar.gz zip) |
| parent | 54b4e80cce0eef459939ad3a3b8dc692e0afc282 | commitdiff |
tg-update.sh: watch out for sneaky blobs
When merging updates throughout the .topdeps graph,
sometimes it's possible to do fast-forward updates.
However, just because a fast-forward update is
possible does not mean it's always correct especially
when it allows .topdeps and/or .topmsg files to sneak
into places where they do not belong.
Avoid this by checking any potential "fast-forards"s
to make sure they satisfy the current top blob constraints
before allowing them to proceed.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
When merging updates throughout the .topdeps graph,
sometimes it's possible to do fast-forward updates.
However, just because a fast-forward update is
possible does not mean it's always correct especially
when it allows .topdeps and/or .topmsg files to sneak
into places where they do not belong.
Avoid this by checking any potential "fast-forards"s
to make sure they satisfy the current top blob constraints
before allowing them to proceed.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
| tg-update.sh | diffblobblamehistory |