git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: uxecw <uxecw@student.kit.edu>
To: <git@vger.kernel.org>
Subject: Bug Report - Git does not require a space between shorthand flags and the commit-message
Date: Thu, 13 Jul 2023 15:04:37 +0200	[thread overview]
Message-ID: <fcdf19b3-269b-aa9f-38c2-d0f775524a89@student.kit.edu> (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)
Rebasing.
I entered `git commit —amend` (one hypen istead of two) accidently and 
it passed as defacto `git commit —all —message "end"`.
I think because of the missing space git should have rejected the given 
input.

What did you expect to happen? (Expected behavior)
Input should have been rejected

What happened instead? (Actual behavior)
`git commit —all —message "end"`

What's different between what you expected and what actually happened?

Anything else you want to add:

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.34.1
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC 
Wed Jun 21 15:35:31 UTC 2 x86_64
compiler info: gnuc: 11.3
libc info: glibc: 2.35
$SHELL (typically, interactive shell): /bin/bash


[Enabled Hooks]
not run from a git repository - no hooks to show


             reply	other threads:[~2023-07-13 13:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:04 uxecw [this message]
2023-07-14  0:48 ` Bug Report - Git does not require a space between shorthand flags and the commit-message brian m. carlson

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=fcdf19b3-269b-aa9f-38c2-d0f775524a89@student.kit.edu \
    --to=uxecw@student.kit.edu \
    --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).