Hanan Arshad proposed porcelain for sharing stashes through a remote. The workflow already works with existing commands: export a stash, push the export to a ref such as refs/stashes/alice/wip, then fetch it into another namespace and run git stash import. The imported stash is an ordinary local stash with the original object ID.

Johannes Sixt objected on principle. He said stashes are strictly personal, short-lived work-in-progress states, and that someone sharing longer-lived work should use a branch. He pointed out that git push origin stash@{0}:refs/stashes/hanan/fix-login already works, and that for a rare operation convenience is not needed. Junio Hamano said he agreed, and that discovery, transfer and clean-up are all easier with branches, which have long had good support for them. He also asked Arshad not to top-post.

Arshad conceded that a git stash publish command would mostly duplicate a single existing push and said he will not pursue it. He is considering a narrower proposal covering the less convenient parts of a temporary handoff: discovering remote stash refs, fetching one into a normal local stash entry, and removing the remote ref.

Arshad described the use case as temporarily handing an unfinished working state to another clone or developer without first making it a normal branch workflow, comparing it to a Perforce shelf. Sixt replied that he remained unhappy with an interface premised on stashes being shareable. No maintainer has endorsed the narrower idea.