From: tlaronde@kergis.com
To: undisclosed-recipients: ;
Subject: [9front] FWIW: kerTeX published as git repos
Date: Tue, 30 Jan 2024 13:18:44 +0100 [thread overview]
Message-ID: <ZbjpJAc0dxQKe2GM@kergis.com> (raw)
FWIW, I have published under:
https://github.com/tlaronde/
risk_comp, kertex_M, kertex_T and kertex_pkg sources.
More easy to browse than the tarballs.
I will accept contribs after review (I believe in managing with a hand
of iron in a glove of lead, the lead adding to the weight when hitting
while being malleable enough to avoid hurting the iron hand):
Violence doesn't solve all the problems... Above all if one
makes the mistake of not hitting hard enough.
KungFuCius
--
Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
reply other threads:[~2024-01-30 12:23 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=ZbjpJAc0dxQKe2GM@kergis.com \
--to=tlaronde@kergis.com \
--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).