On Tue, Apr 16, 2013 at 1:11 PM, Ramkumar Ramachandra
<artag...@gmail.com> wrote:
> Brandon Casey wrote:
>>             # Save another stash here
>>             echo bash >file
>>             git add file
>>             git stash save "something"
>>             # Now git stash show stash^{/quuxery} no longer works.
> Ah, yes.  My stupidity.  Why was I expecting ^{/quuxery} to dig
> through the reflog?
>> An extension to the reflog dwimery that implements @{/<text>} could be
>> interesting though.
> Yeah, this sounds interesting.
> My initial itch that led up to this: I wanted a way to stash something
> away and recover it at a later time predictably for rebase.autostash
> (there might have been other stash invocations in between).
> Originally, I thought I'd need a refs/stashes/* or something of the
> sort to solve this problem, but git-stash.sh hard-codes refs/stash
> everywhere (and so do other things like reflog).  So, I was thinking
> about retrieving it based on commit message, but the solution is still
> short of ideal.  What are your thoughts on my original refs/stashes/*
> idea?

You can create a stash without modifying the refs/stash reflog using
'sha1=`git stash create`' and then later apply it using 'git stash
apply --index $sha1'.  You'll have to reset the work directory
yourself though since 'git stash create' does not do so.  The stash
created this way is just a dangling commit so it will have a lifetime
according to the gc.pruneexpire (default 2 weeks currently).

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to