2 ms·
Not OP, but I've encountered a few situations where the solution was modifying .git/ manually. The one that comes to mind was having two branches with names sep
by AlotOfReading 3y ago
Not OP, but I've encountered a few situations where the solution was modifying .git/ manually. The one that comes to mind was having two branches with names separated only by case on a case sensitive system, and then checking out both on a case insensitive system.
- pmontra 3y agoWouldn't be easier to rename the branches on the case sensitive system (a throw away Linux VM would do), push, pull? Of course if the solution is editing .git/config, that's even easier, but it probably takes more than that.
- AlotOfReading 3y agoIt's been awhile so my memory is fuzzy, but this was at a windows-only shop back before WSL was a thing and getting a VM involved an annoying months-long requisition process. I think the repo state was actually corrupted too, so pull may not have been working.
- zx8080 3y ago> I've encountered a few situations where the solution was modifying .git/ manually Would be very interesting to know the purpose of modifying .git/ manually.