{"thread":{"id":"59679","subject":"git-submodule docs for status command should mention --all option to git describe","startedAt":"2023-05-01T19:22:16Z","lastAt":"2023-05-01T19:22:16Z","messageCount":1,"participants":["Britton Kerin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"476374","messageId":"CAC4O8c9Q4oPP+RgVuOHfz9G8+3v5rDHMXoM_QJvArQGVWSHu-g@mail.gmail.com","threadId":"59679","inReplyTo":null,"subject":"git-submodule docs for status command should mention --all option to git describe","fromName":"Britton Kerin","fromEmail":"britton.kerin@gmail.com","sentAt":"2023-05-01T19:21:58Z","receivedAt":"2023-05-01T19:22:16Z","isPatch":false,"sender":{"key":"britton.kerin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/7434164?v=4"},"body":"The docs currently say:\n\n     status [--cached] [--recursive] [--] [<path>…]\n     Show the status of the submodules. This will print the SHA-1 of\nthe currently checked out\n     commit for each submodule, along with the submodule path and the\noutput of git describe for\n     the SHA-1.\n\nIt took some guessing to figure out that it's actually the output of\ngit describe --all for the SHA-1.\n\ngit describe alone says e.g.:\n\n     fatal: No annotated tags can describe\n'eb44efaaedcca34fc43c451f5659ec2e80bb2bbc'.\n     However, there were unannotated tags: try --tags.\n\nSo I tried that:\n\n     $ git describe eb44efaaedcca34fc43c451f5659ec2e80bb2bbc --tags\n     v0.4.0-devel3-14-geb44efaa\n\nBut that's also not what git submodule status shows in my case:\n\n     $ git submodule status\n     04bd93953af4d0f624a5103a8ac29caa4d0c64c4 contrib (heads/master)\n\nIf I understand correctly git describe will never find heads/ refs\n(barring pathological names) without --all, so it seems that it would\nbe best to short-circuit the above fun by including the --all flag in\nthe above documentation paragraph.\n\nBritton\n"}]}