From: Johannes Sixt <j.sixt@viscovery.net>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: stash refuses to pop
Date: Wed, 11 Apr 2012 07:58:34 +0200 [thread overview]
Message-ID: <4F851D8A.4000501@viscovery.net> (raw)
In-Reply-To: <4F84827B.80104@ubuntu.com>
Am 4/10/2012 20:56, schrieb Phillip Susi:
> On 4/10/2012 2:05 PM, Junio C Hamano wrote:
>> Phillip Susi<psusi@ubuntu.com> writes:
>>
>>> git stash refuses to apply a stash if it touches files that are
>>> modified. Using stash -p to selectively stash some hunks of a file
>>> and then immediately trying to pop that stash causes this failure
>>> every time.
>>
>> I think that is by design.
>
> Being able to push something that you can not pop seems to be broken
> design...
You are trying to abuse git-stash, but it does not cooperate because it
was not designed to be abused ;-) git-stash is not intended as a generic
push-and-pop-my-changes work horse.
The purpose of git-stash is that you can "move away"
- all of your changes to have a clean worktree or
- part of your changes to _create a clean worktree from the remaining
changes_.
That is, before you can think of applying a stash, you are expected to
have cleaned out your worktree.
-- Hannes
next prev parent reply other threads:[~2012-04-11 5:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 17:52 stash refuses to pop Phillip Susi
2012-04-10 18:05 ` Junio C Hamano
2012-04-10 18:56 ` Phillip Susi
2012-04-11 2:47 ` Andrew Ardill
2012-04-11 2:59 ` Phillip Susi
2012-04-14 4:27 ` Andreas Krey
2012-04-14 10:12 ` Jakub Narebski
2012-04-16 1:29 ` Phillip Susi
2012-04-11 7:15 ` Victor Engmark
2012-04-11 5:58 ` Johannes Sixt [this message]
2012-04-11 14:21 ` Phillip Susi
2012-04-12 5:50 ` Johannes Sixt
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F851D8A.4000501@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=psusi@ubuntu.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.