On Sun, Jan 1, 2017 at 4:43 AM, Philip Oakley <philipoakley@xxxxxxx> wrote: > From: "Jacob Keller" <jacob.keller@xxxxxxxxx> >> I do have one comment regarding this series. Is it ever possible for >> an older version of git to be running a process while a new version of >> git which cleans up dirs runs? Is this expected? I just want to make >> sure we don't need to worry about that scenario since otherwise it >> makes it much more challenge. > > > It is easily possible in the Windows environment where the install philosphy > is different, and some external vendor tools may even bring in their own > copy of Git as well. There is also the Portable Git version, so the > possibility of multiple versions running concurrently is there, though it is > on Windows... > > I certainly have a Git-for-Windows published version, and a recent SDK > version on my home machines. > > Ok. >> >> My thought as far as I understand it is that it is possible, because a >> user COULD choose to run both this and an older version, but that it >> is unlikely in practice outside of a few developer boxes who >> periodically switch between versions of git, and are unlikely to >> actually run multiple versions at exactly the same time. >> >> Thanks, >> Jake >> > Philip But how likely is it to end up with differing binaries running on the exact same repository concurrently? Basically, I am trying to see whether or not we could accidentally end up causing problems by trying to race with other git processes that haven't yet been made safe against race? Is the worst case only that some git operation would fail and you would have to retry? Thanks, Jake