From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Alexei Khlebnikov Newsgroups: gmane.emacs.bugs Subject: bug#21559: 25.0.50; auto-revert-mode breaks git rebase Date: Wed, 14 Feb 2018 11:08:53 +0100 Message-ID: References: <87wpvebraz.fsf@smart-cactus.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="001a114b43ac9fb8030565294d3d" X-Trace: blaine.gmane.org 1518626055 9695 195.159.176.226 (14 Feb 2018 16:34:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 14 Feb 2018 16:34:15 +0000 (UTC) To: 21559@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Feb 14 17:34:11 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1em005-0000Xy-DS for geb-bug-gnu-emacs@m.gmane.org; Wed, 14 Feb 2018 17:33:41 +0100 Original-Received: from localhost ([::1]:38061 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1em027-0002wa-Dw for geb-bug-gnu-emacs@m.gmane.org; Wed, 14 Feb 2018 11:35:47 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50334) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1elzwf-0006fg-4o for bug-gnu-emacs@gnu.org; Wed, 14 Feb 2018 11:30:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1elzwZ-0003uX-9z for bug-gnu-emacs@gnu.org; Wed, 14 Feb 2018 11:30:09 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:35162) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1elzwZ-0003te-6S for bug-gnu-emacs@gnu.org; Wed, 14 Feb 2018 11:30:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1elzwY-0001D2-RZ for bug-gnu-emacs@gnu.org; Wed, 14 Feb 2018 11:30:02 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: <87wpvebraz.fsf@smart-cactus.org> Resent-From: Alexei Khlebnikov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 14 Feb 2018 16:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21559 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 21559-submit@debbugs.gnu.org id=B21559.15186257774590 (code B ref 21559); Wed, 14 Feb 2018 16:30:02 +0000 Original-Received: (at 21559) by debbugs.gnu.org; 14 Feb 2018 16:29:37 +0000 Original-Received: from localhost ([127.0.0.1]:43059 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elzw8-0001By-RB for submit@debbugs.gnu.org; Wed, 14 Feb 2018 11:29:37 -0500 Original-Received: from mail-wm0-f47.google.com ([74.125.82.47]:55677) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1elu08-0006tH-41 for 21559@debbugs.gnu.org; Wed, 14 Feb 2018 05:09:20 -0500 Original-Received: by mail-wm0-f47.google.com with SMTP id a84so10175822wmi.5 for <21559@debbugs.gnu.org>; Wed, 14 Feb 2018 02:09:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=z4s3To81GSXtqPAqxDrfWpurYf0BxZI2Moj7rEhjGe0=; b=SYVuvu6iWH7WU7JwbmLjlQ6lReWslSb5MmOB74/wS7f6IcOOtIJVmyBl7prwwUN7ii VgdrqtcqlB4cqVV21a7b3rdE2hmDX5Z3WGJcBwG0cGjn2TSzIVdG/tjshhxlGT0EdYxy 0xkm7pkCMCXDgVpwYUj3kqMi0t/RqLSUW3IhlSD5JPVy6U6PLd9xsT4WF5bqr57hVacT S/loUl4hSX2LFTOj2T0qMhv5gDp0H2p6WegypkhJesPVBmXmQ5MCMgCgPc12v3b5GMna 9kJRzHsaALTpVxP+yBWHOIMAUJz0DMNAMCRiTdc+7plVEqTeAC0VLUgIT00LYFpeAV2r uZpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=z4s3To81GSXtqPAqxDrfWpurYf0BxZI2Moj7rEhjGe0=; b=mv1fwzcvt+3q8ZIJkGDXjutt1f+JzfEuslEMAvPOogNUQMoEf5w5CHdlYVcWE6wIkH Xl+VwkNe4B/ArMAkxca931y7q+zSf6pe8RLN7Sp8sWrzSkpovpJe1dM3Tm4uDIN/Chfx EusUobROPdFeh1ewOz37LQ2qlipevQAsI366Tnxt9g3XZQaz2IvLGGB41jnHxW1bv34m wD0BsrzBFU5F+0eY3FT1TwT6hrFwFyAoH6FniGytMK/gEuvC2AEdUWEwLJQm3iLJni4K JHc9sT7EEd1RQA2EP6fowPtIhES5sEBkCQTOLn8Qiu7vjAdmmu68d4arWoihE/EmQS0b WNQw== X-Gm-Message-State: APf1xPCG7y6pJEKpFiaQ7N+vOLRQvkzUy3px0rF0jUzyua74YB6nPABR Td0X9HGFd+duv8xZfe5jizqXZnzQMLBn3L5KErAyjw== X-Google-Smtp-Source: AH8x2264kR4KZtRFnrXp3Bi4J/LZoA6qvir17jbmWYdnCGr5GKhVRR3/PGa3cFbKQgKIu7S+PKU6BdCPkrO5P9Z5X3w= X-Received: by 10.28.27.139 with SMTP id b133mr2098002wmb.29.1518602953928; Wed, 14 Feb 2018 02:09:13 -0800 (PST) Original-Received: by 10.28.229.138 with HTTP; Wed, 14 Feb 2018 02:08:53 -0800 (PST) X-Mailman-Approved-At: Wed, 14 Feb 2018 11:29:35 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:143274 Archived-At: --001a114b43ac9fb8030565294d3d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Since some version, Git supports "--no-optional-locks" switch and "GIT_OPTIONAL_LOCKS" environment variable for avoiding locking during "git status". That's how they are documented: ---------------------------------------- https://git-scm.com/docs/git#git---no-optional-locks --no-optional-locks Do not perform optional operations that require locks. This is equivalent to setting the GIT_OPTIONAL_LOCKS to 0. https://git-scm.com/docs/git-status#_background_refresh BACKGROUND REFRESH By default, git status will automatically refresh the index, updating the cached stat information from the working tree and writing out the result. Writing out the updated index is an optimization that isn=E2=80=99t strictl= y necessary (status computes the values for itself, but writing them out is just to save subsequent programs from repeating our computation). When status is run in the background, the lock held during the write may conflict with other simultaneous processes, causing them to fail. Scripts running status in the background should consider using git --no-optional-locks status (see git[1] for details). ---------------------------------------- Using this "--no-optional-locks" switch looks like a solution to the issue? --001a114b43ac9fb8030565294d3d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Since some version, Git support= s "--no-optional-locks" switch and "GIT_OPTIONAL_LOCKS"= environment variable for avoiding locking during "git status&q= uot;.

That's how they are documented:

-------------= ---------------------------
https://git-scm.com/docs/git#gi= t---no-optional-locks

--no-opt= ional-locks

Do not perform optional operations that require locks. This is equivalent to setting the GIT_OPTIONAL_LOCKS to 0= .

https://git-scm.com/docs/git-status#_background_refres= h

BACKGROUND REFRESH

By default, git status will automati= cally refresh the index, updating the cached stat information from the work= ing tree and writing out the result. Writing out the updated index is an op= timization that isn=E2=80=99t strictly necessary (status computes the value= s for itself, but writing them out is just to save subsequent programs from= repeating our computation). When status is run in the background, the lock= held during the write may conflict with other simultaneous processes, caus= ing them to fail. Scripts running status in the background should consider = using git --no-optional-locks status (see git[1] for details).
---------= -------------------------------

Using this &q= uot;--no-optional-locks" switch looks like a solution to the is= sue?

--001a114b43ac9fb8030565294d3d--