On Thu, May 13, 2021, at 3:08 AM, Richard Purdie wrote: > > I had a look at the code to try and remind myself why it is doing this.
Thanks! > The best answer I found is that it does support filtered fetching of > remotes, i.e. it can and will only pull the branch it wants/needs rather > than a full repo clone. In the case of a small repo, it doesn't matter > much. For a large repo it can make a significant difference to the speed. This is with `git clone --single-branch`? Makes sense. > We also don't run "test" commands against the remote repo, we figure out > what we want and then get it with small numbers of commands. I think what I'd argue is that in the case where the remote branch is deleted, the tooling should fall back to listing remote branches, sort by most recently updated, and try finding the commit on that. And in practice, explicitly using `main` first in that list would make sense. > Is explicitly specifying the branch along with the repo url such a big > problem? We already have to provide the url, it isn't like we guess that > too. The problem is that your build system is penalizing upstream projects that are trying to migrate to using `main`.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#151702): https://lists.openembedded.org/g/openembedded-core/message/151702 Mute This Topic: https://lists.openembedded.org/mt/82782995/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
