Git development
 help / color / mirror / Atom feed
From: Jon Forrest <nobozo@gmail.com>
To: git@vger.kernel.org
Subject: Is Git Add Supposed to Work Like This (git 2.50)?
Date: Sat, 6 Sep 2025 19:02:53 -0700	[thread overview]
Message-ID: <63045080-74d6-4835-9d9c-4d3558acdbfb@gmail.com> (raw)

(Linux fedora 6.16.4-200.fc42.x86_64)

Let's say I have the file "x" in my working directory, but
not "bogus_file".

If I run

	git add x bogus_file

I get

	fatal: pathspec 'bogus_file' did not match any files

This is what I expect. However, if I look at what's in the index,
"x" doesn't appear. The same thing happens if I specify 15
valid files followed by 1 invalid file.

Apparently the presence of even 1 invalid file invalidates
the whole 'git add' command, no matter how many valid files
are included.

Is this deliberate?

Cordially,
Jon Forrest


             reply	other threads:[~2025-09-07  2:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07  2:02 Jon Forrest [this message]
2025-09-07  8:10 ` Re Is Git Add Supposed to Work Like This (git 2.50)? K Jayatheerth
2025-09-07 23:34 ` Jeff King
2025-09-09 16:00   ` Jon Forrest
2025-09-09 18:33     ` Jon Forrest
2025-09-09 18:42       ` Jeff King
2025-09-09 20:55         ` Junio C Hamano
2025-09-09 21:01           ` Jeff King
2025-09-09 18:40     ` Jeff King

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=63045080-74d6-4835-9d9c-4d3558acdbfb@gmail.com \
    --to=nobozo@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