From: igor@9lab.org
To: 9front@9front.org
Cc: igor@9lab.org, ori@eigenstate.org
Subject: Re: [9front] git/merge: preserve exec bit correctly
Date: Tue, 26 Apr 2022 08:10:47 +0200 [thread overview]
Message-ID: <BDE372576FF428B50D82009AC61BB1C1@9lab.org> (raw)
In-Reply-To: <A4C1418A90DEA2E10B68619869039C86@eigenstate.org>
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.
prev parent reply other threads:[~2022-04-26 6:12 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
2022-04-26 6:10 ` igor [this message]
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=BDE372576FF428B50D82009AC61BB1C1@9lab.org \
--to=igor@9lab.org \
--cc=9front@9front.org \
--cc=ori@eigenstate.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).