From: Michael Haggerty <mhagger@alum.mit.edu>
Date: Thu, 17 Sep 2015 09:40:26 GMT
Subject: Re: [PATCH v4] gc: save log from daemonized gc --auto and print it next time
Message-ID: <55FA8A8A.7000707@alum.mit.edu>
In-Reply-To: <xmqqmvwms6b1.fsf@gitster.mtv.corp.google.com>

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
mhagger@alum.mit.edu