On Thu, Nov 5, 2015 at 11:11 AM, Lyle Ziegelmiller <lyle_z@xxxxxxxxxxx> wrote: > git push --set-upstream has some sort of race condition. Some times when I > execute it, it works. Other times, it does not. Below is from my command > window. I've executed the exact same command (using bash history > re-execution, so I know I didn't make a typo), repeatedly. Notice the last > execution results in an error. I am the only person on my machine. This is > non-deterministic behavior. > > lylez@LJZ-DELLPC ~/gittest/local > $ git push --set-upstream origin localbranch1 > Branch localbranch1 set up to track remote branch localbranch1 from origin. > Everything up-to-date > > lylez@LJZ-DELLPC ~/gittest/local > $ git push --set-upstream origin localbranch1 > Branch localbranch1 set up to track remote branch localbranch1 from origin. > Everything up-to-date > > lylez@LJZ-DELLPC ~/gittest/local > $ git push --set-upstream origin localbranch1 > error: could not commit config file .git/config > Branch localbranch1 set up to track remote branch localbranch1 from origin. > Everything up-to-date > > I'm using Git in a Cygwin window on a 32-bit Windows 10 machine. If I recall correctly, the typical culprit is a Windows virus scanner (or even an indexer) locking the file, so git is unable to manipulate it. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html