{"thread":{"id":"62604","subject":"[help] git status doesn't seem to work.","startedAt":"2024-12-05T19:52:48Z","lastAt":"2024-12-05T21:08:41Z","messageCount":4,"participants":["A bughunter","rsbecker@nexbridge.com","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"508681","messageId":"n8KYxrArhb3MywPvDHVmEz0dka8QYYWikLDZE_aboUX9GBgF2X9uomuxtrPA6VmS33TxXyltJB4xqjALIuprVvE12prKd_ZW4MYM9kC4Qds=@proton.me","threadId":"62604","inReplyTo":null,"subject":"[help] git status doesn't seem to work.","fromName":"A bughunter","fromEmail":"a_bughunter@proton.me","sentAt":"2024-12-05T19:52:37Z","receivedAt":"2024-12-05T19:52:48Z","isPatch":false,"sender":{"key":"a_bughunter@proton.me","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\n\n\n\n[help] git status doesn't seem to work. See how a pull caused updates after status showed \"up to date\"\n\n```\n~/Peeranoia_Framework $ git status\nOn branch main\nYour branch is up to date with 'origin/main'.\n\nnothing to commit, working tree clean\n~/Peeranoia_Framework $ git pull\nEnter passphrase for key '/data/data/com.termux/files/home/.ssh/id_ed25519':\nremote: Enumerating objects: 17, done.\nremote: Counting objects: 100% (17/17), done.\nremote: Compressing objects: 100% (15/15), done.\nremote: Total 15 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0)\nUnpacking objects: 100% (15/15), 6.41 KiB | 312.00 KiB/s, done.\nFrom github.com:freedom-foundation\"up to date\"/Peeranoia_Framework\n   03edf66..4cf4f51  main       -> origin/main\nUpdating 03edf66..4cf4f51\nFast-forward\n README.md | 24 +++++++++++++++++++++---\n 1 file changed, 21 insertions(+), 3 deletions(-)\n~/Peeranoia_Framework $ git status\nOn branch main\nYour branch is up to date with 'origin/main'.\n\nnothing to commit, working tree clean\n```\n\nfrom A_bughunter@proton.me\n\nSent with Proton Mail secure email.\n-----BEGIN PGP SIGNATURE-----\nVersion: ProtonMail\n\nwnUEARYKACcFgmdSBIIJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu\n8pkAALjBAP45ZhMdBcf1zjdJRoyhz32ikG5ndCkNXFn95CpUH0txcwD/WuZQ\nZJCa46Cavsdv6ZL6kFm0w+KA9SEifL1N5eoYgg0=\n=jjzN\n-----END PGP SIGNATURE-----\n"},{"id":"508682","messageId":"048801db4750$97831e70$c6895b50$@nexbridge.com","threadId":"62604","inReplyTo":"n8KYxrArhb3MywPvDHVmEz0dka8QYYWikLDZE_aboUX9GBgF2X9uomuxtrPA6VmS33TxXyltJB4xqjALIuprVvE12prKd_ZW4MYM9kC4Qds=@proton.me","subject":"RE: [help] git status doesn't seem to work.","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2024-12-05T20:02:14Z","receivedAt":"2024-12-05T20:02:35Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On December 5, 2024 2:53 PM, A bughunter wrote:\n>[help] git status doesn't seem to work. See how a pull caused updates after status\n>showed \"up to date\"\n>\n>```\n>~/Peeranoia_Framework $ git status\n>On branch main\n>Your branch is up to date with 'origin/main'.\n>\n>nothing to commit, working tree clean\n>~/Peeranoia_Framework $ git pull\n>Enter passphrase for key '/data/data/com.termux/files/home/.ssh/id_ed25519':\n>remote: Enumerating objects: 17, done.\n>remote: Counting objects: 100% (17/17), done.\n>remote: Compressing objects: 100% (15/15), done.\n>remote: Total 15 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0) Unpacking\n>objects: 100% (15/15), 6.41 KiB | 312.00 KiB/s, done.\n>>From github.com:freedom-foundation\"up to date\"/Peeranoia_Framework\n>   03edf66..4cf4f51  main       -> origin/main\n>Updating 03edf66..4cf4f51\n>Fast-forward\n> README.md | 24 +++++++++++++++++++++---\n> 1 file changed, 21 insertions(+), 3 deletions(-) ~/Peeranoia_Framework $ git status\n\nThis is exactly what git pull is supposed to do. The operation does not\nleave files in an uncommitted state, so the message\n\n>On branch main Your branch is up to date with 'origin/main'.\n>nothing to commit, working tree clean\n\nis 100% correct before and after the pull in your example.\n\n"},{"id":"508686","messageId":"20241205201952.GB2635755@coredump.intra.peff.net","threadId":"62604","inReplyTo":"n8KYxrArhb3MywPvDHVmEz0dka8QYYWikLDZE_aboUX9GBgF2X9uomuxtrPA6VmS33TxXyltJB4xqjALIuprVvE12prKd_ZW4MYM9kC4Qds=@proton.me","subject":"Re: [help] git status doesn't seem to work.","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2024-12-05T20:19:52Z","receivedAt":"2024-12-05T20:19:54Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Dec 05, 2024 at 07:52:37PM +0000, A bughunter wrote:\n\n> [help] git status doesn't seem to work. See how a pull caused updates after status showed \"up to date\"\n> \n> ```\n> ~/Peeranoia_Framework $ git status\n> On branch main\n> Your branch is up to date with 'origin/main'.\n\nThis is comparing your branch with the local tracking branch we have,\nrefs/remotes/origin/main. It doesn't touch the network, and that\ntracking branch is essentially a cache of the last value we fetched.\n\n> ~/Peeranoia_Framework $ git pull\n> Enter passphrase for key '/data/data/com.termux/files/home/.ssh/id_ed25519':\n> remote: Enumerating objects: 17, done.\n> remote: Counting objects: 100% (17/17), done.\n> remote: Compressing objects: 100% (15/15), done.\n> remote: Total 15 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0)\n> Unpacking objects: 100% (15/15), 6.41 KiB | 312.00 KiB/s, done.\n> From github.com:freedom-foundation\"up to date\"/Peeranoia_Framework\n>    03edf66..4cf4f51  main       -> origin/main\n> Updating 03edf66..4cf4f51\n> Fast-forward\n>  README.md | 24 +++++++++++++++++++++---\n>  1 file changed, 21 insertions(+), 3 deletions(-)\n\nThis pull is doing a fetch under the hood (since pull is essentially\n\"fetch + merge\"). It updates the tracking branch origin/main, at which\npoint a \"git status\" would show that your local branch is not up to\ndate. But since it then immediately merges the result, you find that\nafterwards:\n\n> ~/Peeranoia_Framework $ git status\n> On branch main\n> Your branch is up to date with 'origin/main'.\n\n...your branch is now up to date.\n\nThis is all working as expected. If you want a more up-to-date view of\n\"origin/master\" when you run your \"git status\", try \"git fetch\" to hit\nthe network first.\n\nYou might also find more information in:\n\n  https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches\n\n-Peff\n"},{"id":"508693","messageId":"LgXFUHKOZ9fW4415YWA5y3is9qOJfG04kXCgoAtEB5Oe7YrvY1RuzfogI4ISvdjV76-bn1orZp8FG7KkDlJ5CC0zkWTqMaXDwkAenywEqJM=@proton.me","threadId":"62604","inReplyTo":"20241205201952.GB2635755@coredump.intra.peff.net","subject":"Re: [help] git status doesn't seem to work.","fromName":"A bughunter","fromEmail":"a_bughunter@proton.me","sentAt":"2024-12-05T21:08:28Z","receivedAt":"2024-12-05T21:08:41Z","isPatch":false,"sender":{"key":"a_bughunter@proton.me","avatar":null},"body":"-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA512\n\n\n\n\nGood answer Peff. It answers a lingering question here https://lore.kernel.org/git/0fyZjFuLfvDKSV32a70rBZ4q-iPMLmZtv4ITVBuqoUbtyUiD9CAbaCFgOKNsSh9Rq0tMszzyT1-kqf9bsWroZxEJXW_-Fg-VvBHKUqfCZZM=@proton.me/\n\nfrom A_bughunter@proton.me\n\nSent with Proton Mail secure email.\n\nOn Thursday, December 5th, 2024 at 14:19, Jeff King <peff@peff.net> wrote:\n\n> On Thu, Dec 05, 2024 at 07:52:37PM +0000, A bughunter wrote:\n> \n> > [help] git status doesn't seem to work. See how a pull caused updates after status showed \"up to date\"\n> > \n> > ```\n> > ~/Peeranoia_Framework $ git status\n> > On branch main\n> > Your branch is up to date with 'origin/main'.\n> \n> \n> This is comparing your branch with the local tracking branch we have,\n> refs/remotes/origin/main. It doesn't touch the network, and that\n> tracking branch is essentially a cache of the last value we fetched.\n> \n> > ~/Peeranoia_Framework $ git pull\n> > Enter passphrase for key '/data/data/com.termux/files/home/.ssh/id_ed25519':\n> > remote: Enumerating objects: 17, done.\n> > remote: Counting objects: 100% (17/17), done.\n> > remote: Compressing objects: 100% (15/15), done.\n> > remote: Total 15 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0)\n> > Unpacking objects: 100% (15/15), 6.41 KiB | 312.00 KiB/s, done.\n> > From github.com:freedom-foundation\"up to date\"/Peeranoia_Framework\n> > 03edf66..4cf4f51 main -> origin/main\n> > Updating 03edf66..4cf4f51\n> > Fast-forward\n> > README.md | 24 +++++++++++++++++++++---\n> > 1 file changed, 21 insertions(+), 3 deletions(-)\n> \n> \n> This pull is doing a fetch under the hood (since pull is essentially\n> \"fetch + merge\"). It updates the tracking branch origin/main, at which\n> point a \"git status\" would show that your local branch is not up to\n> date. But since it then immediately merges the result, you find that\n> afterwards:\n> \n> > ~/Peeranoia_Framework $ git status\n> > On branch main\n> > Your branch is up to date with 'origin/main'.\n> \n> \n> ...your branch is now up to date.\n> \n> This is all working as expected. If you want a more up-to-date view of\n> \"origin/master\" when you run your \"git status\", try \"git fetch\" to hit\n> the network first.\n> \n> You might also find more information in:\n> \n> https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches\n> \n> -Peff\n-----BEGIN PGP SIGNATURE-----\nVersion: ProtonMail\n\nwnUEARYKACcFgmdSFkoJkKkWZTlQrvKZFiEEZlQIBcAycZ2lO9z2qRZlOVCu\n8pkAABrFAQCbDOZHArmE9Tb1IEfKiptP1L2sKGjWvMRq2HcVzC1yfgD/Q83n\nS+eVEQTC65XKGxb4a3v9RSOiXgFxfrAE6dBd+wY=\n=ZGvg\n-----END PGP SIGNATURE-----\n"}]}