git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Another Email <yetanotheroneemail@gmail.com>
To: git@vger.kernel.org
Subject: Issue when adding new files to staged changes using interactive mode
Date: Wed, 29 Jul 2020 00:10:19 +0100	[thread overview]
Message-ID: <5BDF4B85-7AC1-495F-85C3-D429E3E51106@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)
git init test
cd test
echo "test" > test.txt
git add -AN
git add -p

What did you expect to happen? (Expected behavior)
The file would be added to staged changes after confirming each individual change in an interactive mode.

What happened instead? (Actual behavior)
I get "error: test.txt: already exists in index".

What's different between what you expected and what actually happened?
The file wasn't added to staged changes.

Anything else you want to add:
It used to work before updating to 2.28, previous version was 2.26 if I'm not mistaken. I couldn’t find any mention of changes in the recent release notes.

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.28.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Darwin 19.5.0 Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64
compiler info: clang: 11.0.3 (clang-1103.0.32.62)
libc info: no libc information available
$SHELL (typically, interactive shell): /bin/zsh


[Enabled Hooks]


             reply	other threads:[~2020-07-28 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 23:10 Another Email [this message]
2020-07-29 18:58 ` Issue when adding new files to staged changes using interactive mode Raymond E. Pasco
2020-07-29 21:30   ` Raymond E. Pasco
2020-07-29 22:33     ` Another Email
2020-07-31 19:51 ` Taylor Blau

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=5BDF4B85-7AC1-495F-85C3-D429E3E51106@gmail.com \
    --to=yetanotheroneemail@gmail.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. 
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 NNTP newsgroup(s).