git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: JoséQuintas <jmcquintas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Windows 7 - long/short and upper/lower filename
Date: Fri, 07 Aug 2015 16:03:21 +0200	[thread overview]
Message-ID: <466225b8050e58deaf5ffa4ad41d64b9@www.dscho.org> (raw)
In-Reply-To: <55BFDAB0.8010306@gmail.com>

Hi,

On 2015-08-03 23:18, JoséQuintas wrote:
> I am using Windows 7 64 bits.

... and Git version... ?

> I have a filename called ze_xmlfun.prg
> Last week gitgui shows 2 changed files: ZE_XML~1.PRG and ze_xmlfun.prg
> At momment I can't update this file, because get a error.
> Try delete file, update one name each time, but same error.
> Seems that a unique file is considered as 2 files, and this causes error.

This is no longer allowed in the most recent Git for Windows 1.x versions, for exactly the reason you mentioned: the short name is actually referring to the same file as the long name. Therefore, short names will be refused.

Unfortunately, you will have to fix this issue in your repository yourself. It will most likely entail something like `git rm --cached ZE_XML~1.PRG && git commit -s -m "Remove bogus file"`

> When do a search in history, upper/lower case must be the same as in git
> control.
> If upper/lower is changed, is considered a new file.
> How to configure git to work allways using lower case on Windows?

There is no such configuration. If you have a file with an undesired file name, you have to rename it. You can use `git mv` for that.

If the file name differs only in case, you will have to do a little dance like `git mv MYFILE myfile.bak && git mv myfile.bak myfile`

> Is there a plugin or a tool to make this, to new files and to update in
> git repository?

No, not unless you write one.

> Note: gitgui is a gui tool for git, ok, but once it uses git, may be
> this feature/change need to be made in git.

If you have an idea how to incorporate this into Git's source code, it would be a splendid idea to contribute that change to this mailing list.

Ciao,
Johannes

      reply	other threads:[~2015-08-07 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 21:18 Windows 7 - long/short and upper/lower filename JoséQuintas
2015-08-07 14:03 ` Johannes Schindelin [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=466225b8050e58deaf5ffa4ad41d64b9@www.dscho.org \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jmcquintas@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).