{"thread":{"id":"63376","subject":"Re: Possible BUG: git stash -m picks branch name from submodule","startedAt":"2025-04-30T14:05:20Z","lastAt":"2025-04-30T14:05:20Z","messageCount":1,"participants":["Alex Arques"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"517022","messageId":"GVYP280MB02088CB5884078D16260E61D93832@GVYP280MB0208.SWEP280.PROD.OUTLOOK.COM","threadId":"63376","inReplyTo":null,"subject":"Re: Possible BUG: git stash -m picks branch name from submodule","fromName":"Alex Arques","fromEmail":"alexander.arques@piabgroup.com","sentAt":"2025-04-30T14:05:17Z","receivedAt":"2025-04-30T14:05:20Z","isPatch":false,"sender":{"key":"alexander.arques@piabgroup.com","avatar":null},"body":"I also encountered this today on “git version 2.49.0.windows.1” in a repository with two submodules, both which are set up to track “master”.\n\nWhenever I do “git stash push” with a message on the main repository my stash message seems to be prepended with “On master: “.\nThis only works correctly if I omit the “-m” or “—message” part of “git stash push”.\n\ngit stash with no arguments outputs this:\nSaved working directory and index state WIP on <current branch>\n\nWhile git stash -m “[…]” outputs this:\nSaved working directory and index state On master: […]\n\nWhich is not what I want because “git stash list” now gives me confusing output.\nIt seems like I have encountered the same bug? <current branch> on the main repository is NOT “master”.\n"}]}