Thank you for your criticism, I will keep it in mind and submit more detailed descriptions in the future. > By the way, isn't this a typical time-of-check to time-of-use bug? > Not the problem with the fix in the patch but in the original, but regardless of > whose fault it is, it may be good to fix it (outside the topic of this patch). Is concurrent use even meant to be supported in general? I have not done a thorough review, but judging from what I have seen so far, I highly doubt that the majority of git-p4.py was written with potential concurrency problems in mind. Best regards, Moritz