git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ng, Alexander" <ang@slac.stanford.edu>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Git pop/apply/drop with stash message
Date: Wed, 28 Sep 2022 17:45:18 +0000	[thread overview]
Message-ID: <CH2PR07MB81876BD87634A5C62BF0BC12EC549@CH2PR07MB8187.namprd07.prod.outlook.com> (raw)

Hello, I am experiencing the following issue. Thanks for reviewing.
What did you do before the bug happened? (Steps to reproduce your issue)
1. Changes in working directory
2. git stash push -m "test" :to stash changes in stash with message "test"
3. git stash pop stash^{/test}  :pop stash 
 
What did you expect to happen? (Expected behavior)
git pops the stash with message "test", applying stash to files and removing stash from list
 
What happened instead? (Actual behavior)
Returns 'stash^{/test}' is not a stash reference
 
What's different between what you expected and what actually happened?
Git stash pop and git stash drop do not allow for referencing specific stashes by message.
The desired behavior does work for git stash apply stash^{/test}, but I need to also remove stash from list.
 
Anything else you want to add:
 
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
 
 
[System Info]
git version:
git version 2.35.4
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 2.6.32-754.43.1.el6.x86_64 #1 SMP Wed Nov 17 07:27:32 EST 2021 x86_64
compiler info: gnuc: 4.4
libc info: glibc: 2.12
$SHELL (typically, interactive shell): /bin/bash
 
 
[Enabled Hooks]

                 reply	other threads:[~2022-09-28 17:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CH2PR07MB81876BD87634A5C62BF0BC12EC549@CH2PR07MB8187.namprd07.prod.outlook.com \
    --to=ang@slac.stanford.edu \
    --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).