From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kraymer <kraymer@gmail.com>, git@vger.kernel.org
Subject: Re: Bug report: branch display in git stash output
Date: Sat, 23 Oct 2021 19:10:39 +0700 [thread overview]
Message-ID: <376fa19b-0e3f-1ccb-6c25-c9aa86fc0707@gmail.com> (raw)
In-Reply-To: <CAAjS6zO2E043KEcqEJr_5QbtdZEjxVWObCc518Ti3sW-p6LX5A@mail.gmail.com>
On 23/10/21 14.21, Kraymer wrote:
> What did you do before the bug happened? (Steps to reproduce your issue)
>
> ❯ git checkout -b branch/with/slash
> Switched to a new branch 'branch/with/slash'
> ❯ echo "foobar" > foobar.txt
> ❯ git stash
> Saved working directory and index state WIP on slash: 41dc5da git:
> update .gitconfig
>
> What did you expect to happen? (Expected behavior)
>
> ❯ git stash list
> stash@{0}: WIP on branch/with/slash: 41dc5da git: update .gitconfig
>
> What happened instead? (Actual behavior)
>
> ❯ git stash list
> stash@{0}: WIP on slash: 41dc5da git: update .gitconfig
>
> What's different between what you expected and what actually happened?
>
> the displayed branch name in `git stash` output is truncated
I can reproduce the issue using this reproducer:
```
mkdir test && cd test &&
git init &&
# make initial commit first, since git stash requires it
echo "./" > slashdot &&
git commit -m "slashdot" &&
# stash WIP
git checkout -b slash/dot &&
echo "slashdot" >> slashdot &&
git stash push -m "slashdot"
```
Note that when stashing, the message says "Saved working directory and
index state On dot: slashdot" although we are currently on `slash/dot`
branch.
--
An old man doll... just what I always wanted! - Clara
prev parent reply other threads:[~2021-10-23 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 7:21 Bug report: branch display in git stash output Kraymer
2021-10-23 12:10 ` Bagas Sanjaya [this message]
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=376fa19b-0e3f-1ccb-6c25-c9aa86fc0707@gmail.com \
--to=bagasdotme@gmail.com \
--cc=git@vger.kernel.org \
--cc=kraymer@gmail.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.
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).