git-switch(1) then git-pull(1)
- Reply: Nuno Teixeira : "Re: git-switch(1) then git-pull(1)"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 02 Dec 2022 08:04:05 UTC
I'm confused. If a switch is intended to update things, then how can an immediately subsequent pull lead to updates? % git -C /usr/ports switch main && git -C /usr/src switch main Already on 'main' Your branch is up to date with 'freebsd/main'. M sys/netgraph/bluetooth/hci/ng_hci_cmds.c M sys/netgraph/bluetooth/hci/ng_hci_evnt.c M sys/netgraph/bluetooth/include/ng_hci.h Already on 'main' Your branch is up to date with 'origin/main'. % git -C /usr/ports pull --ff-only && git -C /usr/src pull --ff-only remote: Enumerating objects: 3284, done. remote: Counting objects: 100% (840/840), done. remote: Compressing objects: 100% (3/3), done. remote: Total 3284 (delta 837), reused 837 (delta 837), pack-reused 2444 Receiving objects: 100% (3284/3284), 1.92 MiB | 1.11 MiB/s, done. Resolving deltas: 100% (1985/1985), completed with 474 local objects. From https://git.freebsd.org/ports fb6a9af3e898..80afc63eeb99 main -> freebsd/main 749ca3ec2e60..c3552efe398e 2022Q4 -> freebsd/2022Q4 Updating fb6a9af3e898..80afc63eeb99 ^C % cat /usr/ports/.git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "freebsd"] url = https://git.freebsd.org/ports.git fetch = +refs/heads/*:refs/remotes/freebsd/* [branch "main"] remote = freebsd merge = refs/heads/main % Git - git-switch Documentation <https://git-scm.com/docs/git-switch>