From: Justin Tang <jutang@ixl.com>
To: git@vger.kernel.org
Subject: git bug
Date: Thu, 8 Feb 2024 11:32:48 -0800 [thread overview]
Message-ID: <CAO18WYyQas36PNz20+pRt0usGqZwrhVYDbQfPZnHEVD8esfoyQ@mail.gmail.com> (raw)
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
add a new file to the git directory, untracked. with some path path/to/file
I wanted to use git diff on untracked files, so I added the file as an
empty file to git, with:
git add --intent-to-add path/to/file
Then I wanted to stash my changes, with:
git stash save
What did you expect to happen? (Expected behavior)
My changes to be stashed.
What happened instead? (Actual behavior)
I can't stash my changes, git stash save or git stash save --include-untracked.
I was getting this error:
error: Entry 'path/to/file' not uptodate. Cannot merge. Cannot save
the current worktree state
What's different between what you expected and what actually happened?
umm
Anything else you want to add:
Anything else you want to add:
I 'fixed' this by removing the empty file with git rm -r --cached path/to/file
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.38.4
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 3.10.0-1127.13.1.el7.x86_64 #1 SMP Tue Jun 23 15:46:38
UTC 2020 x86_64
compiler info: gnuc: 10.2
libc info: glibc: 2.17
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
commit-msg
post-commit
post-rewrite
pre-commit
pre-push
prepare-commit-msg
next reply other threads:[~2024-02-08 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 19:32 Justin Tang [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-04 23:42 git bug moti sd
2024-02-05 6:47 ` Patrick Steinhardt
2023-04-14 9:41 Git bug Gabriel Furstenheim Milerud
2023-04-14 16:07 ` René Scharfe
[not found] ` <CAJN3DWpvh8uHnRFnaPgg8U6dW=3xP9YULBe-xfeTAg2SV7K+oQ@mail.gmail.com>
2023-04-17 9:46 ` Gabriel Furstenheim Milerud
2023-04-14 8:29 Gabriel Furstenheim Milerud
2023-04-14 9:26 ` Kristoffer Haugsbakk
2020-08-06 14:59 git bug PANEL Christian
2020-08-06 14:48 PANEL Christian
2020-08-06 20:23 ` René Scharfe
2020-08-07 0:02 ` Jeff King
2020-08-10 5:56 ` René Scharfe
2020-08-10 17:20 ` PANEL Christian
2012-10-22 16:28 git BUG Коньков Евгений
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=CAO18WYyQas36PNz20+pRt0usGqZwrhVYDbQfPZnHEVD8esfoyQ@mail.gmail.com \
--to=jutang@ixl.com \
--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).