git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Concept question about push/pull stashes

From
Cc.buhtz@posteo.jp <c.buhtz@posteo.jp>
Date
Sep 1, 2021, 07:44 UTC
Message-ID
<8d2f05e6f4ff9855460402e8cdafd7e7@posteo.de>

Hello, my question has to goals. I want to understand the design decisions behind a (missing) feature and and wan't to explore the needs of other users before I start to implement something.

There is no usual way to exchange stashes with other repos/users. Stashes are code snippets that are unfinished and not clean enough to commit them anywhere not even in another branch.

Why? What is the concept behind this? I am sure this was well thought. I just try to understand.

A feature like this is often asked by users when you asked the search engine of your trust.

One workaround is to simply commit the stashed code, push/pull it, checkoutit into the other repo and delete the last commit.

The other workaround is to create a patch-file from a stash. But then the question is how to exchange this file?

Why not use the git infrastructure itself?

I have workaround in my mind. I couuld use a script wich creates patch files for each existing stash and commit them into the repo. Thats all. To keep the repo "clean" the path files could be archived into a hidden (dotted filed) tar file. Or the tar file could be stored inside the ".git" folder if there is a way.

I am interested in your thoughts about this.
Next: Philip Oakley
Message 1 of 2 in “Concept question about push/pull stashes”
  1. c.buhtz@posteo.jpSep 1, 2021
  2. Philip OakleySep 1, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.