For the SDK Quick Start Guide documentation, I had completed the updating of Ubuntu packages, and installation of required additional packages. Next is to proceed the part of downloading the SDK, but I couldn’t run the command which is to clone into “VisionFive2”.
Okkk, now I understand the reasons of not getting to clone the github VF2 correctly. Will try to refer the link you provided and follow the steps. Really thanks a lot @mzs for the points and tips. Thank you <3
To contribute, the first step would more be to make your own fork on Github, then close your fork, work there, and when happy with something to share, create a pull request from your fork, better than working with only a local copy as creating pull request going to be a bit hard this way
I did say that you may need to edit .git/config
I use vi as my editor, because that is the editor that is on every UNIX system I’ve ever used. It is insanely powerful (search for “vi cheat sheet”), but has a unforgiving brick wall learning curve.
Change, I’ll just do one as an example - but change them all, “git@github.com:starfive-tech/buildroot.git” to be “https://github.com/starfive-tech/buildroot.git”.
I got the idea already. Before this I dont understand the steps of cloning the files, now I get it the steps and the command ways already. Thanks a lot. Sorry disturbing you. <3
The danger in automating any change is that one typo can mangle a lot of files. What you intended was 's#git@github.com:#https://github.com/#g' or 's/git@github.com:/https:\/\/github.com\//g' but what you told the machine to do is ‘s/git@github.com:/https://github.com//g’ spot the problem ?