From: "Torsten Bögershausen" <tboegi@web.de>
To: Angelo Melonas <angelomelonas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Possible minor bug in Git
Date: Sat, 2 Feb 2019 06:38:28 +0000 [thread overview]
Message-ID: <20190202063828.4kjtdmrsm7g4eyg3@tb-raspi4> (raw)
In-Reply-To: <CAHYHVPJdbEOPaAoyAhOtJ+wkeXZdowAVqe1Tp_=LOKzuuzA+wQ@mail.gmail.com>
On Fri, Feb 01, 2019 at 10:02:50AM +0200, Angelo Melonas wrote:
> Hi Torsten,
>
> Thank you so much for getting back to me.
>
> Unfortunately, I believe there is a misunderstanding, as I may have
> explained what I found to be a possible bug incorrectly.
> The file that is originally added (and then later modified) is never
> renamed or moved.
> As you will see below, when a user attempts to add a file, but with
> the incorrect case, the Git CLI responds the same way it would if a
> file was correctly added (i.e., by displaying nothing).
> However, in the above case, when you enter "git status", you find that
> the file was never actually added, and remains unstaged.
> A possible solution to this can be a simple error message similar to
> attempting to add a file with its name misspelt.
>
> Using your example, I have illustrated this in the text below:
>
> C:\Example>git init
> Initialized empty Git repository in C:/Example/.git/
>
> C:\Example>echo AAA > AA.txt
>
> C:\Example>git add AA.txt
>
> C:\Example>git commit -m AA.txt
> [master (root-commit) d550af0] AA.txt
> 1 file changed, 1 insertion(+)
> create mode 100644 AA.txt
>
> C:\Example>echo BB > AA.txt
>
> C:\Example>git status
> On branch master
> Changes not staged for commit:
> (use "git add <file>..." to update what will be committed)
> (use "git checkout -- <file>..." to discard changes in working directory)
>
> modified: AA.txt
>
> no changes added to commit (use "git add" and/or "git commit -a")
>
> C:\Example>git add Aa.txt
>
> C:\Example>git status
> On branch master
> Changes not staged for commit:
> (use "git add <file>..." to update what will be committed)
> (use "git checkout -- <file>..." to discard changes in working directory)
>
> modified: AA.txt
>
> no changes added to commit (use "git add" and/or "git commit -a")
>
> C:\Example>git add A.txt
> fatal: pathspec 'A.txt' did not match any files
>
> C:\Example>git add AA.txt
>
> C:\Example>git status
> On branch master
> Changes to be committed:
> (use "git reset HEAD <file>..." to unstage)
>
> modified: AA.txt
>
> I am looking forward to hearing from you again.
>
> Kind regards,
> Angelo Melonas
>
Actually yes, you can call this a minor bug.
Does anybody want to work on it ?
May be as a first-time-Git contribution ?
next prev parent reply other threads:[~2019-02-02 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 7:01 Possible minor bug in Git Angelo Melonas
2019-01-31 7:29 ` Angelo Melonas
2019-01-31 20:34 ` Torsten Bögershausen
2019-02-01 8:02 ` Angelo Melonas
2019-02-02 6:38 ` Torsten Bögershausen [this message]
2019-02-06 22:17 ` Giuseppe Crinò
2019-02-07 19:41 ` Johannes Schindelin
2019-02-08 17:43 ` Torsten Bögershausen
2019-02-09 18:19 ` Philip Oakley
2019-02-10 22:46 ` Giuseppe Crino'
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190202063828.4kjtdmrsm7g4eyg3@tb-raspi4 \
--to=tboegi@web.de \
--cc=angelomelonas@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).