Note that you can even run: git pull origin main featureīut you almost certainly should not. If and when you do run any of these, all of these positional arguments are passed to git fetch. With or without these options, though, you can run: git pullįor example. Note that the pull documentation says that some options are passed to one or the other or to both, and that there's a fair bit of overlap in some options (e.g., all take -q for quiet and -v for verbose). See its documentation for the complete list, then compare these options to those for git fetch and for git rebase and git merge. The git pull command has a lot of options. □ It's also gained a feature or two since then, enough that at least a few hardcore "anti pull" people like me are now willing to actually use the thing. Then it has these tests and then it eventually runs this other command." The result is that it runs much faster on Windows, and is much harder to explain. While git pull still effectively runs git fetch followed by a second Git command, you can no longer point to the shell script and say: "See, here at this line, it runs git fetch. In Git 2.11, the old git pull shell script was formally retired. Some people are still using Git 1.7.x for some strange reason, so be aware that you could hit them. Specifically, Git 1.8.4 fixed something eventually declared to be a bug. However, between Git 1.7 and Git 2.0, there were some updates to them. In any case, remote-tracking names now exist. The remote-tracking names ( origin/master and the like) take over a job that would in the past require using a local branch name.īut all these things are still supported and some of them are still described as "the way to do things" in some (ancient) documents, so you can still use the old crude methods.
0 Comments
Leave a Reply. |