From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 12127 invoked from network); 26 Apr 2022 06:12:19 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 26 Apr 2022 06:12:19 -0000 Received: from mail.9lab.org ([168.119.8.41]) by 9front; Tue Apr 26 02:10:55 -0400 2022 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=9lab.org; s=20210803; t=1650953447; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=Ah6/FiUyf+WOtoksc0Vzf6Mxb8Gslc184mJGL5DMTO8=; b=VWteXqME3nxjhy12X5mWrdO1QBtngoi1hnTrMH67ZxB8gM8hXoLnzOLk/HaRUcBc2gfHva Ku/av/ugVj6vQeKPITgzpSSfoNn8xyd3C77FvMHZKKDJNMrjkIl9/TB1EdpGSDWABtCc+U LuCRtOBOI6KOdB0vVuE/1eUhd86BgzU= Received: from rob.9lab.home (host-185-64-155-70.ecsnet.at [185.64.155.70]) by mail.9lab.org (OpenSMTPD) with ESMTPSA id 7f1c3e36 (TLSv1.2:ECDHE-RSA-CHACHA20-POLY1305:256:NO); Tue, 26 Apr 2022 08:10:47 +0200 (CEST) Message-ID: To: 9front@9front.org CC: igor@9lab.org, ori@eigenstate.org Date: Tue, 26 Apr 2022 08:10:47 +0200 From: igor@9lab.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: non-blocking agile strategy hosting Subject: Re: [9front] git/merge: preserve exec bit correctly Reply-To: 9front@9front.org Precedence: bulk Quoth ori@eigenstate.org: > Quoth igor@9lab.org: > > When trying to switch between branches using git/branch things fall > > over with the below error. > > > > I have done no further debugging so far. Hence, the issue could still > > be between keyboard and chair. More debug info to follow off list... > > A suicide is definitely not between keyboard and chair :) > > What would be useful would be a 9p trace of the messages; > I'd like to know what we cloned the fid from, and what we > tried to do with it before clunking. > > git/fs -d > > will print a 9p trace. Confirmed that the issue exists without applying the patches. Hence this is an existing issue and not related to the changes you asked to be tested. Will try to debug further in the course of next week.