cannot 'git commit -m ...' in DOSprompt

Bug #759301 reported by Michael X
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DOSprompt
In Progress
High
Michael X

Bug Description

example:
C:\Users\mike\git\DOSprompt> git commit -m 'errorlevel added, new developer_mode setting, fixed if not running real commands'
error: pathspec 'added,' did not match any file(s) known to git.
error: pathspec 'new' did not match any file(s) known to git.
error: pathspec 'developer_mode' did not match any file(s) known to git.
error: pathspec 'setting,' did not match any file(s) known to git.
error: pathspec 'fixed' did not match any file(s) known to git.
error: pathspec 'if' did not match any file(s) known to git.
error: pathspec 'not' did not match any file(s) known to git.
error: pathspec 'running' did not match any file(s) known to git.
error: pathspec 'real' did not match any file(s) known to git.
error: pathspec 'commands'' did not match any file(s) known to git.

Michael X (crazedpsyc)
Changed in dosprompt:
importance: Undecided → High
assignee: nobody → Crazed Psyc (crazedpsyc)
Michael X (crazedpsyc)
Changed in dosprompt:
status: New → In Progress
Michael X (crazedpsyc)
Changed in dosprompt:
milestone: none → 2.0
Revision history for this message
Michael X (crazedpsyc) wrote :

This bug exists with anything like this:
command -o 'message'

Revision history for this message
Michael X (crazedpsyc) wrote :

Found issue, quoted text is not properly recognized as a single argument, instead being split along with everything else.

Changed in dosprompt:
milestone: 2.0 → 2.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.