From: "Torsten Bögershausen" <tboegi@web.de>
To: Mateusz M <mateuszx90@gmail.com>, git@vger.kernel.org
Subject: Re: Bug-directors upper letters names.
Date: Sat, 06 Sep 2014 15:45:17 +0200 [thread overview]
Message-ID: <540B0FED.1080507@web.de> (raw)
In-Reply-To: <CAEyutAhj4UMWPHV-d24yjx36Q9mjKHdGArpZxpTQS2REfJkREA@mail.gmail.com>
On 2014-09-06 08.05, Mateusz M wrote:
> Last days I found special case. A
> changed packages name (all letter to lowercase). After merge with
> other branch there were still uppercase letters.All the rest code is
> after refactoring.
> Is it a bug ?
Unless you provide more information what had been done,
what is the expected result versus what is on the file system,
this question is impossible to answer (at least for me)
Do you use a case-insensitive file system like Windows or Mac OS?
What does "git status" say?
What does "git ls-files say ?
What does "ls -1" say ?
prev parent reply other threads:[~2014-09-06 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-06 6:05 Bug-directors upper letters names Mateusz M
2014-09-06 13:45 ` Torsten Bögershausen [this message]
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=540B0FED.1080507@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=mateuszx90@gmail.com \
/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).