git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[BUG] git restore: typo in error message "could not resolve ource"

From
ZZZhelyo Zhelev <zhelyo@gmail.com>
Date
Dec 22, 2025, 09:16 UTC
Message-ID
<CAMxgZ8KqU9BUJ6T7DLct3CaEh9EYdcMO=dBAMPyQsb=knekSuQ@mail.gmail.com>

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) I executed the following command in repository: git restore -source my_base_branch I have reproduced this on both Windows (git version 2.52.0.windows.1) and Ubuntu (git version 2.52.0).

What did you expect to happen? (Expected behavior) The error message should be: fatal: could not resolve source

What happened instead? (Actual behavior) The error message is: fatal: could not resolve ource

What's different between what you expected and what actually happened? There is a typo in the displayed error message - the first letter 's' is missing from the word "source" in the output.

Anything else you want to add: The bug is present in the latest stable version 2.52.0 on both Linux and Windows.

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.52.0.windows.1
cpu: x86_64
built from commit: 2912d8e9b8253723974b7baf1c890273b1a1c5bd
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
rust: disabled
feature: fsmonitor--daemon
libcurl: 8.17.0
OpenSSL: OpenSSL 3.5.4 30 Sep 2025
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
uname: Windows 10.0 26100
compiler info: gnuc: 15.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
Next: brian m. carlson
Message 1 of 5 in “[BUG] git restore: typo in error message "could not resolve ource"”
  1. Zhelyo ZhelevDec 22, 2025
  2. brian m. carlsonDec 22, 2025
  3. Junio C HamanoDec 22, 2025
  4. checkout: quote invalid treeish in error messagebrian m. carlson, Dec 24, 2025
  5. Junio C HamanoDec 24, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.