From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] hgfs(4) getrevinfo patch
Date: Sat, 7 Dec 2019 02:58:48 +0100 [thread overview]
Message-ID: <22352BA19B6B1246008535C82F34C10E@felloff.net> (raw)
In-Reply-To: B502F295245F8E7687F9A256E946FDEE@musolino.id.au
read the comment you removed. you'd also need to
change fsstat().
it was not done because this would mean we have to
extract, decompress and and parse the revision content
when reading dirctories for every single file. very expensive.
--
cinap
reply other threads:[~2019-12-07 1:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=22352BA19B6B1246008535C82F34C10E@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).