summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-release-process.xml
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-07-19 16:22:12 +0100
commitef3209ba8f9271f3c31704f9f98a35ecb6bb90c5 (patch)
tree0abafdc52d7a2fd671772b928bd210703418b41a /documentation/ref-manual/ref-release-process.xml
parent3ef26fead43d27558cd860fdf871d94944ac8f97 (diff)
downloadpoky-ef3209ba8f9271f3c31704f9f98a35ecb6bb90c5.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: 6e527ea72b0816bf5f454473faf6523c365daa18) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 820ab886e79eea516560c0c008e4cf059c6e11a3) Signed-off-by: Steve Sakoman <steve@sakoman.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-release-process.xml')
0 files changed, 0 insertions, 0 deletions