On 09/16/2015 06:00 PM, Junio C Hamano wrote: > *1* But one "gc" could be foreground gc that does not write to a log > file and the other "gc" could be background that does write to a > log file, so this cannot be the primary way to avoid double > execution.
^^^ This was the point that was confusing me. If this is not one of the roles of the log file, then things are easier. If you decide to go the route of tempfile/lockfile modifications, feel free to CC me for feedback. Michael -- Michael Haggerty mhag...@alum.mit.edu -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
