summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/tests/fetch-testdata/debian/pool/main/d/db5.3/index.html
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2020-07-08 12:07:42 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-09-08 14:46:02 +0100
commit53f6c01fae28d6c8451d68a26145f896129ed172 (patch)
tree2d4b75daef191fc091b3b9cb2ac431293854f454 /bitbake/lib/bb/tests/fetch-testdata/debian/pool/main/d/db5.3/index.html
parent5408e48d374fc741fa46b57ddfd8a537843bda6f (diff)
downloadpoky-53f6c01fae28d6c8451d68a26145f896129ed172.tar.gz
bitbake: fetch2: Change git fetcher not to destroy old references
It looks like we're about to see a lot of changes in branch names in repos. If we have the prune option here, those old names are lost, the changes propagate to our source mirrors and our old releases break. We have the force option so any replaced references should be replaced, its only orphaned branches which will now be preserved. I believe this behaviour will cause us fewer problems given the changes that look likely to happen. (Bitbake rev: e2fc4147bbe436ac79de187d92d3bc80a8a95349) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/tests/fetch-testdata/debian/pool/main/d/db5.3/index.html')
0 files changed, 0 insertions, 0 deletions