From: c.buhtz@posteo.jp
To: git@vger.kernel.org
Subject: Concept question about push/pull stashes
Date: Wed, 01 Sep 2021 07:44:23 +0000 [thread overview]
Message-ID: <8d2f05e6f4ff9855460402e8cdafd7e7@posteo.de> (raw)
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 reply other threads:[~2021-09-01 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 7:44 c.buhtz [this message]
2021-09-01 9:23 ` Concept question about push/pull stashes Philip Oakley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d2f05e6f4ff9855460402e8cdafd7e7@posteo.de \
--to=c.buhtz@posteo.jp \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).