Git will see the previous object already in your Git database, assume it was already written and simply reuse it. If you try to check out that object again at some point, you’ll always get the data of the first object.
I updated to 17.1.5 (from 17.1.3) yesterday and was immediately hit with the issue described above. Using the “safe directory” fix for either the path to my repo or the global wildcard did not work. My repository was sitting on a mapped network drive. The mapped drive is to a Syno...
Git next inspects the existing index to determine if an entry for that folder\file name already exists with the same SHA-1. If so, it locates the blob object in the .git\objects folder and updates its date-modified time (Git will never overwrite ob-jects that already exist in the repo...
I don't really trust MSYSTEM and MINGW_MOUNT_POINT at this stage ;-) If git.exe sets MSYSTEM, for example, it will not have the expected value. Member dscho commented Apr 28, 2021 I opened git-for-windows/build-extra#338 to help with this. 👍 1 This was referenced May 8, 20...
first on the command line, and force the command to treat end-user input as non-options, has been to use "--" as the delimiter, but that would not work for commands that use "--" as a delimiter between revs and pathspec. * A mechanism to affect the default setting for a (related...
@ayufan I've updated this MR based on the modified release: structure as discussed. It needs some more tests (I will add them). But, I'm blocked on one thing and was wondering if you could look over it? I used descr instead of description as it was conflicting with Gitlab::Config:...
I will add that there was a file with the name PG_VERSION in my (plain) data folder. that value in the plain folder was 10. So my question is why was it trying to create data.11? Now that I have re-updated to LATEST I have a data.10, data.9.6, and data. The PG_VERSION ...
I was not able to find an open or closed issue matching what I'm seeing Setup Which version of Git for Windows are you using? Is it 32-bit or 64-bit? $ git --version --build-options ** git version 2.11.1.windows.1 built from commit: 1c18...
using Windows git. The 'Native' ssh workaround was not working for me because my ssh key is protected with a passphrase. Although my git bash setup loads ssh-agent and prompts me to enter the passphrase when I open git bash, that instance of ssh-agent was evidently not...
We can also go the other way. Pull them from the repository to the staging and then move them to the working but this isn’t something we would usually do. Usually we would pull from the repository directly to the working tree. In the process staging will be updated as well. ...