0

when I'm trying to clone using ssh, cloning is succeeded but checkout fails.. Linux guys have no problem with the same operation

Here is my screen

Any ideas?

Zoe
  • 27,060
  • 21
  • 118
  • 148
Arkadi
  • 1,153
  • 1
  • 14
  • 35
  • 1
    And what does `git status` tell you? – kan Jun 21 '17 at 11:24
  • Shows big list of deleted files and small list of untracked files – Arkadi Jun 21 '17 at 12:17
  • And what the recommended `checkout` command does tell you? – kan Jun 21 '17 at 13:06
  • Anything specific about the files? Windows has some weird restrictions on file names. E.g. a file or dir `com1` could not be created. It could have restricted characters e.g. `:` or `?`. – kan Jun 21 '17 at 13:08
  • @kan there are not restricted characters, before moving on gerrit I used to work with the same code using git (without gerrit) – Arkadi Jun 21 '17 at 13:13
  • files could have been added recently. Gerrit could not affect checkout anyhow. – kan Jun 21 '17 at 13:24
  • I just ran git checkout and seems there's issue with longer names than allowed in windows.. is there any fix for this? – Arkadi Jun 21 '17 at 13:33
  • Check your disk writing permission, is empty disk space enough? – Vy Do Jun 21 '17 at 14:14
  • The only fix is to not to use long names or Windows. Even if git would be able to create such file names, you may experience similar problems using another tools. Try to checkout into a shorter name folder e.g. "C:\my\" – kan Jun 21 '17 at 14:27
  • Possible duplicate of [Filename too long in git for windows](https://stackoverflow.com/questions/22575662/filename-too-long-in-git-for-windows) – kan Jun 21 '17 at 14:28

0 Answers0