From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] inconsistencies after a sysupdate
Date: Mon, 28 Jun 2021 14:33:44 -0400 [thread overview]
Message-ID: <03E3343806CB95B4F9FF59695ED41C31@eigenstate.org> (raw)
In-Reply-To: <4B18B9CC-E8DB-4D27-AFCC-8FF66B2E5DAC@gmail.com>
Quoth Xiao-Yong Jin <meta.jxy@gmail.com>:
> After a sysupdate, I currently have
>
> extern Point pos(Point);
> ; git/walk sys/src/cmd/vt
> T sys/src/cmd/vt/cons.h
> T sys/src/cmd/vt/fs.c
> T sys/src/cmd/vt/main.c
> T sys/src/cmd/vt/mkfile
> T sys/src/cmd/vt/termcap
> T sys/src/cmd/vt/vt.c
>
>
> So git/walk is wrong. How do I fix this?
What are the permissions on those files? We had
some issues where we would:
1) set permissions overly tightly when updating
(644/755, rather than 664, 775), so that
future updates would not be able to modify
those files.
fix: b904edadd8869787b4419ce93c1c29b5beee3556
2) were overly lax in checking for success when
updating files in git/branch and git/revert,
and marking them clean when we failed to update.
fix: 682aabf9f692f310ad910910073d8f9d3839b716
If you were bitten by these bugs, reset the
permissions, and then git/add them to reset
the cache.
next prev parent reply other threads:[~2021-06-28 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 17:18 Xiao-Yong Jin
2021-06-28 18:33 ` ori [this message]
2021-06-28 18:57 ` Xiao-Yong Jin
2021-06-30 0:47 ` ori
2021-07-04 23:53 ` kvik
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=03E3343806CB95B4F9FF59695ED41C31@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).