From: ori@eigenstate.org
To: 9front@9front.org, 9fans@9fans.net
Subject: git/serve, git/compat
Date: Sun, 06 Sep 2020 14:46:50 -0700 [thread overview]
Message-ID: <B678CBD7CA8ABC0D9C128DF4FE365C84@eigenstate.org> (raw)
Hey,
I try not to be too verbose about new features landing in git9, but
I think these warrant some noise. Both git/compat and git/serve
have landed in the last few days.
Git/compat is a script that drops you into a new rc shell with
a 'git' script in $path. This git script provides enough of the
upstream git interface that 'go get' and friends work out of the
box, as long as you're in a git repository. Thanks to halfwit
for doing the work on this!
% git/compat
nested% cd $gorepo
nested% go get ./...
Git/serve is exactly what it sounds like: A git server that runs
on plan 9. It supports both read-only and read-write access.
# read-only git://$host server, works with git
% aux/listen1 'tcp!*!9418' git/serve
Once that's running, you can clone from it using any git client
that supports the git:// protocol
unix$ git clone git://host/path/to/repo.git
p9% git/clone git://host.com/path/to/repo
You can also tunnel it over TLS with plan 9 auth, if you want
authenticated pushes:
% aux/listen1 -t 'tcp!*!9418' tlsclient -a git/serve -wr`{pwd}
With this, you currently need a plan 9 git client, since unix
git doesn't know how to tunnel over tlsclient or authenticate
with an auth server:
p9% git/clone hjgit://host.com/path/to/repo
But we can probably get a simple remote helper for unix git that
will dial using a plan9port copy of tlsclient:
https://rovaughn.github.io/2015-2-9.html
There are still rough edges:
Git/compat only works under a git repository. There are some
commands that 'go get' invokes when run outside of a repository
that need some work.
Git/serve does not currently support bare repositories, so
all repositories served must have a '.git' directory inside
them:
% ls /usr/ori/srv/git9
.git/
It's acceptably fast for small repositories, but there's a lot
of low hanging fruit to pick. And of course, it's only been
tested rather lightly.
next reply other threads:[~2020-09-06 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 21:46 ori [this message]
2020-09-07 3:40 ` [9fans] " Lucio De Re
2020-09-07 3:40 ` Lucio De Re
2020-09-07 4:53 ` [9front] " Jens Staal
2020-09-10 1:35 ` [9fans] " ori
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=B678CBD7CA8ABC0D9C128DF4FE365C84@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.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).