# Git for Windows/ bash does not like Julia

**URL:** https://discourse.julialang.org/t/git-for-windows-bash-does-not-like-julia/100316
**Category:** General Usage
**Tags:** question
**Created:** [June 14, 2023, 7:43am UTC](https://discourse.julialang.org/t/git-for-windows-bash-does-not-like-julia/100316 "2023-06-14T07:43:17Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![PetrKryslUCSD](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/petrkryslucsd/32/215825_2.png) [@PetrKryslUCSD](https://discourse.julialang.org/u/PetrKryslUCSD)
#### Post date: [June 14, 2023, 12:53pm UTC](https://discourse.julialang.org/t/git-for-windows-bash-does-not-like-julia/100316/7 "2023-06-14T12:53:51Z")

</div>

One only should use programs on the WSL side to access files then. Accessing files from both Windows programs and WSL-run programs may lead to corrupted contents due to locking:

> **[Never create or change Linux files using Windows Apps and Tools](https://www.thewindowsclub.com/change-linux-files-using-windows-tools)**
>
> Events like data corruption or damaged Linux environment can occur when you try to create Linux files using Windows tool. So what should you do?

Potential performance gain:

> [@Windows 11 versus WSL2: Need for Speed](https://discourse.julialang.org/t/windows-11-versus-wsl2-need-for-speed/99086):
>
> Could one gain a significant advantage using Julia in Linux running within WSL2 compared to the Windows version? Package instantiation. 239 dependencies, always starting from blank slate (no depot). Julia Version 1.9.0 Commit 8e63055292 (2023-05-07 11:25 UTC) Platform Info: OS: Windows (x86\_64-w64-mingw32) CPU: 8 × Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz WORD\_SIZE: 64 LIBM: libopenlibm LLVM: libLLVM-14.0.6 (ORCJIT, icelake-client) Threads: 1 on 8 virtual cores Environment: JULI…

---

_[View the full topic](https://discourse.julialang.org/t/git-for-windows-bash-does-not-like-julia/100316)._