From: Ori Bernstein <ori@eigenstate.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Git/fs: Possibly Usable
Date: Mon, 8 Jul 2019 12:54:55 -0700 [thread overview]
Message-ID: <20190708125455.ccc7e65e95c42201d8c601cf@eigenstate.org> (raw)
In-Reply-To: <46E7EE42925499BF1B9558D2423340AA@eigenstate.org>
On Mon, 1 Apr 2019 21:41:09 -0700
ori@eigenstate.org wrote:
> It was mentioned on this list a short while ago. Now, it's
> more or less at the point where it works for me. Expect
> many bugs and problems, and many more missing tools, but
> "the rest is just scripting".
An update: I'm now using this git implementation on a daily
basis. It's hosting its own development now, and tons of
bugs have been fixed.
All commits in the git mirror here were made with git9 on 9front:
https://github.com/oridb/git9
I'm also keeping the old mirror in hg alive:
https://bitbucket.org/oridb/git9
There's one incompatibility that I'm aware of with 9legacy, where
I use `$split{...} syntax in rc to make files with spaces work
cleanly. I don't think 9legacy imported that patch from 9atom.
The remaining missing bits, in my mind:
- UI polish; There's some thought needed about how
the exposed functionality should work.
- Patch import/export: probably git/diff -[pa] for
generating or importing `git format-patch` compatible
style diff.
- Rebase-like functionality would be nice.
- (Low priority, probably won't do it myself, but I'd
take a patch): HTTP protocol. Most places (including
github) serve up git protocol URLS, in the form
git://github.com/user/repo
--
Ori Bernstein <ori@eigenstate.org>
next prev parent reply other threads:[~2019-07-08 19:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 4:41 ori
2019-04-02 6:10 ` Skip Tavakkolian
2019-04-02 13:32 ` Dave MacFarlane
2019-04-02 14:37 ` Kyohei Kadota
2019-04-03 10:38 ` Giacomo
2019-04-03 18:29 ` Skip Tavakkolian
2019-04-03 20:14 ` David du Colombier
2019-04-03 20:23 ` Ori Bernstein
2019-04-04 0:00 ` Skip Tavakkolian
2019-04-04 0:34 ` Kurt H Maier
2019-04-04 1:22 ` Ori Bernstein
2019-04-14 9:58 ` [9fans] UI design | enhancements Darren Wise
2019-04-14 11:30 ` Ethan Gardener
2019-04-14 14:19 ` hiro
2019-04-15 5:07 ` Lucio De Re
2019-04-15 6:12 ` Bakul Shah
2019-04-15 6:25 ` Devine Lu Linvega
2019-04-15 6:41 ` Michael Misch
2019-04-15 7:24 ` Bakul Shah
2019-04-15 11:20 ` hiro
2019-04-15 14:27 ` Kurt H Maier
2019-04-15 19:59 ` Ethan Gardener
2019-04-15 20:04 ` Michael Misch
2019-04-15 15:10 ` Chris McGee
2019-04-15 15:44 ` Darren Wise
2019-04-15 18:11 ` ab
2019-07-08 19:54 ` Ori Bernstein [this message]
2019-07-12 18:27 ` [9fans] Git/fs: Possibly Usable Patrick Marchand
2019-07-12 20:21 ` Steve Simon
2019-07-21 21:06 ` clueelf
2019-07-25 21:59 ` Ori Bernstein
2019-08-05 18:43 ` Skip Tavakkolian
2019-08-05 21:17 ` erik quanstrom
2019-08-05 21:22 ` erik quanstrom
2019-08-09 5:56 ` Ori Bernstein
2019-04-02 5:36 cinap_lenrek
2019-04-02 15:35 ori
2019-04-03 16:02 ori
2019-04-03 16:59 ` Giacomo
2019-04-03 18:41 ` Cull
2019-04-03 18:44 ` Ori Bernstein
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=20190708125455.ccc7e65e95c42201d8c601cf@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9fans@9fans.net \
/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).