From: firstname.lastname@example.org To: email@example.com Cc: firstname.lastname@example.org, email@example.com Subject: Re: [9front] git/merge: preserve exec bit correctly Date: Tue, 19 Apr 2022 10:18:43 -0400 [thread overview] Message-ID: <A4C1418A90DEA2E10B68619869039C86@eigenstate.org> (raw) In-Reply-To: <662EE35E4A9773AA51270EF917573B51@9lab.org> Quoth firstname.lastname@example.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.
next prev parent reply other threads:[~2022-04-19 14:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-16 21:13 ori 2022-04-16 21:46 ` ori 2022-04-19 8:46 ` igor 2022-04-19 14:18 ` ori [this message] 2022-04-26 6:10 ` igor
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=A4C1418A90DEA2E10B68619869039C86@eigenstate.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [9front] git/merge: preserve exec bit correctly' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).