From: Johannes Sixt <email@example.com>
To: Yuri <firstname.lastname@example.org>
Cc: Git Mailing List <email@example.com>
Subject: Re: [feature suggestion] Add 'git stash export', 'git stash import' commands to allow to backup stash externally
Date: Thu, 6 May 2021 08:43:55 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Am 06.05.21 um 08:12 schrieb Yuri:
> On 5/5/21 11:07 PM, Johannes Sixt wrote:
>> I would argue that you are doing something wrong if your stashes are
>> particularly valuable. If you regularly revert temporary, but precious
>> work, then you should commit the work and mark it with a branch tip or
> No, it is work in progress. I begin to work on some modification or
> update, discover some issue, and stash the update until this issue is
> It could take days, weeks, months to resolve them.
I know. But, as I said, when you turn away from your current work, which
is precious, then you should make a commit, in particular, when you can
forsee that you might not be able to come back soon.
A 'git stash' is really only intended as a short-term
make-the-worktree-temporarily-clean auxiliary storage. It is not
intended as a long-term storage. For long-term storage, use branches.
"Short term" is measured in seconds (rebase --autostash), minutes,
perhaps hours, but certainly not weeks or months.
At least, that's how I understand (and use) it.
next prev parent reply other threads:[~2021-05-06 6:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 19:51 [feature suggestion] Add 'git stash export', 'git stash import' commands to allow to backup stash externally Yuri
2021-05-05 20:07 ` Randall S. Becker
2021-05-05 20:11 ` Yuri
2021-05-06 2:22 ` Junio C Hamano
2021-05-06 6:07 ` Johannes Sixt
2021-05-06 6:12 ` Yuri
2021-05-06 6:43 ` Johannes Sixt [this message]
2021-05-06 6:58 ` Yuri
2021-05-06 8:38 ` Junio C Hamano
2021-05-06 8:41 ` Yuri
2021-05-06 9:09 ` Junio C Hamano
2021-05-06 10:23 ` Felipe Contreras
2021-05-06 8:40 ` Felipe Contreras
2021-05-06 8:45 ` Yuri
2021-05-06 10:45 ` Felipe Contreras
2021-05-06 14:10 ` Theodore Ts'o
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:
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 \
* 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
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).