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, o...@eigenstate.org <o...@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. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T9c456b888b0c38ed-M33808e421c99249bf77972cd Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
