# Re: Possible BUG: git stash -m picks branch name from submodule

1 messages from 2025-04-30 to 2025-04-30. Participants: Alex Arques.
Thread: https://gitlist.dev/t/63376

## Alex Arques, 2025-04-30 14:05

Subject: Re: Possible BUG: git stash -m picks branch name from submodule
Message-ID: <GVYP280MB02088CB5884078D16260E61D93832@GVYP280MB0208.SWEP280.PROD.OUTLOOK.COM>
URL: https://gitlist.dev/e/GVYP280MB02088CB5884078D16260E61D93832%40GVYP280MB0208.SWEP280.PROD.OUTLOOK.COM

```
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”.

Whenever I do “git stash push” with a message on the main repository my stash message seems to be prepended with “On master: “.
This only works correctly if I omit the “-m” or “—message” part of “git stash push”.

git stash with no arguments outputs this:
Saved working directory and index state WIP on <current branch>

While git stash -m “[…]” outputs this:
Saved working directory and index state On master: […]

Which is not what I want because “git stash list” now gives me confusing output.
It seems like I have encountered the same bug? <current branch> on the main repository is NOT “master”.

```