From: Fazlul Shahriar <fshahriar@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] git9 on 9legacy
Date: Fri, 6 Dec 2019 02:27:22 -0500 [thread overview]
Message-ID: <CAA2CNPapriAFXfJH_qRH=VoZ2BJfcOxcwaXJ4Wu_CX50jg-PSQ@mail.gmail.com> (raw)
In-Reply-To: <F1A51E7B9393C16D5F351D7C34C9A95C@eigenstate.org>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
Very cool. I just tried and it seems to work.
patch/apply rc-line-split
>
This patch does not apply cleanly on 9legacy because of conflict with
rc-badrunes patch
(see http://www.9legacy.org/patch.html) which is included in 9legacy CD
image.
I've installed the commands in a "git9" directory instead of "git", so it
doesn't conflict with the 9legacy git script (
http://www.9legacy.org/9legacy/tools/git), which I still want to have
around for 'go get'. It's possible we can have a more complete git script
with the help of git9.
fhs
[-- Attachment #2: Type: text/html, Size: 996 bytes --]
next prev parent reply other threads:[~2019-12-06 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 5:35 ori
2019-12-06 7:27 ` Fazlul Shahriar [this message]
2019-12-06 7:46 ` [9fans] " ori
2019-12-06 6:15 kokamoto
2019-12-06 6:20 ` 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='CAA2CNPapriAFXfJH_qRH=VoZ2BJfcOxcwaXJ4Wu_CX50jg-PSQ@mail.gmail.com' \
--to=fshahriar@gmail.com \
--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).