From: Lucio De Re <lucio.dere@gmail.com>
To: ori@eigenstate.org
Cc: 9fans@9fans.net
Subject: Re: [9fans] Getting git9 -- moved to github.
Date: Sat, 20 Jun 2020 17:58:08 +0200 [thread overview]
Message-ID: <CAJQ9t7jfH0TbMPu7MwTF1eeZuvDe6a_wJsXWPOz-HFFXJmSD4g@mail.gmail.com> (raw)
In-Reply-To: <CAJQ9t7jotbA_SwEQeW7vGXoOc+A4Jomz4XLntpgSyGNPQZ-=5Q@mail.gmail.com>
I guessed my way around the p9p lib9p and libthread facilities and
squeezed some degree of p9p portability into a recent version of Ori's
git9.
It can be found, warts and all: github.com/lootch/git9
My aim was to operate across platforms on a single version of Git, one
with the Plan 9 philosophy behind it (I am deeply thankful to Ori for
creating the foundations for that).
Sadly, besides all the likely mistakes I have no doubt made in my
limited comprehension of multithreading, I definitely could not find
sufficient prior art to model serving the gitfs synthetic filesystem
outside of the p9p environment (announce it on net!*!git, say). It
does rather seem that the necessary thread/9p functions were not
ported to p9p.
I am aware that the modified version is not likely to even compile in
the Plan 9 environment, I will attend to that soon.
If anyone is at all interested in this kind of convergence and can
guide further efforts on my part, I would gladly accept their
suggestions.
Not much to be gained by pointing out to me that this exercise is
wasteful. I have a bee in my bonnet about ridding Linux of its Posix
legacy and moving to a p9p-friendly environment.
Lucio.
> On 2/3/20, ori@eigenstate.org <ori@eigenstate.org> wrote:
>>
>> Yes. git9 takes URLs. This is why I posted a link to the spec that we
>> should follow. I will take patches that bring us in compliance with
>> https://raw.githubusercontent.com/git/git/master/Documentation/urls.txt
PS: I didn't keep that promise, did I?
I replied to Ori's mail at the time, but now I am surprised to
discover what it was all about. I suspect old age is playing tricks on
my memory.
next prev parent reply other threads:[~2020-06-20 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 17:03 ori
2020-01-27 21:23 ` [9fans] " Sergey Zhilkin
2020-02-02 9:58 ` Lucio De Re
2020-02-02 10:35 ` kvik
2020-02-02 14:39 ` Lucio De Re
2020-02-02 22:47 ` hiro
2020-02-02 23:28 ` cinap_lenrek
2020-02-03 0:55 ` ori
2020-02-03 0:57 ` ori
2020-02-03 4:07 ` Lucio De Re
2020-02-03 4:11 ` ori
2020-02-03 7:39 ` Lucio De Re
2020-02-03 10:01 ` hiro
2020-02-03 11:10 ` Lucio De Re
2020-02-03 13:54 ` hiro
2020-02-03 14:40 ` Lucio De Re
2020-02-03 16:14 ` ori
2020-02-04 4:07 ` Lucio De Re
2020-06-20 15:58 ` Lucio De Re [this message]
2020-02-03 20:42 ` cinap_lenrek
2020-02-04 4:03 ` Lucio De Re
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=CAJQ9t7jfH0TbMPu7MwTF1eeZuvDe6a_wJsXWPOz-HFFXJmSD4g@mail.gmail.com \
--to=lucio.dere@gmail.com \
--cc=9fans@9fans.net \
--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).