Double quotes inside a commit message split the arguments

Symptom

git commit -m "... "ok:1284"처럼 ..."
error: pathspec '남길' did not match any file(s) known to git

(The "pathspec" git complains about is a Korean word from the middle of the message.)

Cause

PowerShell re-parses arguments before handing them to a native exe. A double quote inside the string terminates the quoting, and from that point the rest is split on whitespace. A word in the middle of your message suddenly becomes a pathspec.

Fix

• Don't put double quotes in the message (the only bulletproof option)
• Otherwise: single quotes, backtick escapes, or git commit --file <tempfile>
• Multi-line messages: single-quoted here-string @'...'@, and the closing '@ must sit in column 0

Verification

git log -1 --format=%B shows what was actually stored.

---

---