From: "Torsten Bögershausen" <tboegi@web.de>
To: Aaron Gray <aaronngray.lists@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [bug] Possible Windows 'git mv' bug
Date: Sun, 31 Jan 2016 16:52:31 +0100 [thread overview]
Message-ID: <56AE2DBF.1010502@web.de> (raw)
In-Reply-To: <CANkmNDd8GJmKGw9zToKS1ML3tg9Cx2iYQM0E8iHCO2TuQfwmAQ@mail.gmail.com>
On 2016-01-31 15.03, Aaron Gray wrote:
> Hi,
>
> I think I have found a possible difference in behaviour between
> Windows git commandline distro and Linux git
>
> basically If I do a :-
>
> git mv logger.h Logger.h
>
> I get the following :-
>
> fatal: destination exists, source=lib/logger.h, destination=lib/Logger.h
>
> It looks and smells like a bug to me !
Which version of Git are you using ?
Because it is fixed in the latest version in Git and Git for Windows.
next prev parent reply other threads:[~2016-01-31 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 14:03 [bug] Possible Windows 'git mv' bug Aaron Gray
2016-01-31 14:50 ` Johannes Sixt
2016-01-31 15:05 ` Doug Kelly
2016-01-31 15:36 ` Aaron Gray
2016-01-31 15:38 ` Aaron Gray
2016-01-31 15:52 ` Torsten Bögershausen [this message]
2016-02-01 6:32 ` Johannes Schindelin
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=56AE2DBF.1010502@web.de \
--to=tboegi@web.de \
--cc=aaronngray.lists@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.
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).