From: sl@stanleylieber.com
To: 9front@9front.org
Subject: 9base fork renamed to frontbase
Date: Fri, 9 Sep 2016 22:22:26 -0400 [thread overview]
Message-ID: <98ab3a0d59e391622efc1962fb3e4174@dl.attlocal.net> (raw)
Frontbase is a fork of the suckless 9base tree made immediately before
they switched to git:
https://code.9front.org/hg/frontbase
Its purpose is to provide a basic set of Plan 9 utilities in the
spirit of the original 9base. Simple shell tools, now with 33% more
German ("Our Germans are better than their Germans") engineering.
Frontbase could be considered a pared down companion to front9port,
the as-yet nascent, 9front-related fork of plan9port.
Even before frontbase forked, suckless had agreed to include several
changes from 9front that never made it back into plan9port. Changes
already applied include:
- Various fixes and updates to rc(1).
- Patched read(1).
- Added rm(1).
- Added ssam(1).
- Added urlencode(1).
- More stuff obscured by opaque commit messages.
Proposed new changes:
- Use $9FRONT instead of $PLAN9 to avoid stepping on 9base or
plan9port.
- Add u9fs.
- Add file(1) from 9front.
Future plans:
- Diff existing commands and libraries against 9front.
- FreeBSD port/package.
- OpenBSD port/package.
I haven't done any of this stuff yet but if there are no objections I
plan to begin shortly.
sl
next reply other threads:[~2016-09-10 2:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 2:22 sl [this message]
2016-09-10 3:27 ` [9front] " Kurt H Maier
2016-09-10 3:41 ` sl
2016-09-10 4:28 ` Kurt H Maier
2016-09-10 6:42 ` Ian Sutton
2016-09-11 1:43 ` sl
2016-09-11 6:40 ` Kurt H Maier
2016-09-11 9:52 ` Ian Sutton
2016-09-11 9:58 ` Ian Sutton
2016-09-11 23:39 ` kokamoto
2016-09-12 0:10 ` kokamoto
2016-09-11 1:45 ` sl
2016-09-11 5:51 ` kokamoto
2016-09-11 6:05 ` stanley lieber
2016-09-11 14:39 ` Dave MacFarlane
2016-09-10 12:14 ` kokamoto
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=98ab3a0d59e391622efc1962fb3e4174@dl.attlocal.net \
--to=sl@stanleylieber.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).