All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Jarek <wodka.jaroslaw@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Case insensitive when file mv
Date: Mon, 04 Jun 2012 18:35:55 +0200	[thread overview]
Message-ID: <4FCCE3EB.4070607@web.de> (raw)
In-Reply-To: <D62ABB09-AB7B-474E-8CDE-579AD30C58AE@gmail.com>

On 04.06.12 12:36, Jarek wrote:
> Hope it covers everything:
> 
> $ git mv solJW.R solRandom.r
> $ git mv solRandom.r solRandom.R
> fatal: destination exists, source=solRandom.r, destination=solRandom.R
> $ ls
> mouse_evaluator.R mouse_world.R     scenariusze.R     sol1.R            sol2.R            sol3.R            solRandom.r
> $ git mv solRandom.r solRandom.R
> fatal: destination exists, source=solRandom.r, destination=solRandom.R
> $?
> -bash: 128: command not found
> $ git mv solRandom.r solRandom.X
> $ git mv solRandom.X solRandom.R
> $ man git
> $ git --version
> git version 1.7.5.4
> $ touch abc
> $ touch Abc
> $ git add abc
> $ git add Abc
> $ 
> 
> 
> Didn't have time to check whether is it a known bug or already solved in the latest version.
> 
> Kind regards,
> Jarosław Wódka.--
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hej Jarek,
That's a known limitation on case insensitve file system under Windows or Mac OS.
We had a diskussion about this some time ago:

<http://git.661346.n2.nabble.com/PATCH-v2-Allow-git-mv-FileA-fILEa-on-case-ignore-file-systems-td6187510.html>

/Torsten

      reply	other threads:[~2012-06-04 16:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-04 10:36 Case insensitive when file mv Jarek
2012-06-04 16:35 ` 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=4FCCE3EB.4070607@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=wodka.jaroslaw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.