From: Pushkar Singh Date: Wed, 04 Nov 2026 17:34:20 GMT Subject: [PATCH v3 0/2] maintenance: improve lock acquisition failure handling Message-ID: <20261104173422.20725-1-pushkarkumarsingh1970@gmail.com> In-Reply-To: <20261102122955.143018-2-pushkarkumarsingh1970@gmail.com> Greetings, This series improves how "git maintenance" handles failures to acquire the maintenance lock. The first patch changes the handling of lock acquisition failures so that manual invocations report an error and return a non-zero exit status, while automatic invocations print a warning and exit successfully. The second patch adds a Trace2 data event to make it easier to identify cases where automatic maintenance is repeatedly skipped due to lock acquisition failures. Changes in v3: - Split the changes into two separate patches: one for lock failure handling and another for Trace2 instrumentation. - Use `strerror(err)` consistently for reporting lock acquisition failures in Trace2. - Deduplicate the diagnostic message construction while preserving the distinction between warnings and errors. Thanks, Pushkar Pushkar Singh (2): maintenance: report lock acquisition failures maintenance: trace lock acquisition failures