From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] UNIX git push to git9 server possible?
Date: Wed, 19 Mar 2025 13:20:19 -0500 [thread overview]
Message-ID: <580c1db9-60b2-4bfe-9889-e8a5291af636@posixcafe.org> (raw)
In-Reply-To: <E150F16432297BD64A5ACCEA208957E9@chrisfroeschl.de>
On 3/19/25 11:43, chris@chrisfroeschl.de wrote:
> I'm hosting a git9 server as described in https://orib.dev/githosting.html
>
> Although, this works fine, I'm more frequently forced to work from UNIX like
> systems. This, as mentioned, does only allow read access via git://
>
> I was wondering, if there exists a workaround/solution besides copying updates
> to a plan 9 machine and commit/push from there using hjgit with appropriate
> factotum credentials.
>
> Perhaps I'm just unaware of an obvious way to handle the authentication otherwise...
>
My UNIX tlsclient[0] can do this, its not super polished but it does work.
You might need to tweak it a bit for your specific environment.
Thanks,
moody
[0] https://shithub.us/moody/tlsclient/HEAD/info.html
prev parent reply other threads:[~2025-03-19 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 16:43 chris
2025-03-19 18:20 ` Jacob Moody [this message]
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=580c1db9-60b2-4bfe-9889-e8a5291af636@posixcafe.org \
--to=moody@posixcafe.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).