Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you an example analysis of the git fallback version and then return the latest branch git pull failure. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

General description

In an article to solve the problem of gti branch switching, everyone should have this situation, that is, when the latest git code is compiled, it is found that the latest code has bug, and some problem points are not confirmed, then you want to go back to the branch for compilation, debugging and analysis, and finally return to the latest branch, or the modified git push code for compilation.

But have you ever encountered such a situation? I also print out the branch information through git log, then switch to an older branch with git branch to compile the package under yocto, and keep prompting me an error when I switch back to the normal branch for git pull.

The log information is as follows:

You are not currently on a branch.

Please specify which branch you want tomerge with.

See git-pull (1) for details.

Git pull

I. the first step in solving the problem

Google Baidu bing search, I also found an article similar to my problem in stackoverflow. I used the method they provided to operate and found that it could solve the problem of code update.

According to the suggestion, I will go directly to the designated branch for git pull

Second, the second step in solving the problem

Although the problem has been solved for the time being, I am still a little uncomfortable. Because the new method only avoids the problem and does not solve the problem at a deeper level. So I began to read the article again to find a better solution.

I saw that some people suggested that I should first push up the existing branches and pull them down. And some asked me to switch remote branches.

But they all failed. So sometimes a good-looking answer may not necessarily solve your problem.

Then I checked branch again, and at this time I saw the record of branch switching.

I'll just switch over.

Successful git pull at this time

In fact, in the end, I found that the problem was also very simple. I was in a hurry at the beginning, looking for answers everywhere. Maybe if you think about it, you may have a better solution.

The above is an example of the failure of the latest branch git pull returned after the fallback version of git shared by the editor. If you happen to have similar doubts, please refer to the above analysis for understanding. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.