From: stanley lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] rc: unix bits removed
Date: Tue, 17 May 2016 20:42:00 -0400 [thread overview]
Message-ID: <449FF310-DCE6-4FC2-9DC4-3A54B8896C09@stanleylieber.com> (raw)
In-Reply-To: <97183dbcc380d94ebd53bfc76a5f3110@felloff.net>
>do you mean that some 9base package refers to files from 9front
>mercurial tip?
No, I was asking (without having checked) if the p9p/9base rc uses those files from whatever version of rc they are derived. The reason I asked is because whenever I have time I will be trying to sync frontbase (our fork of 9base) with 9front. I was wondering if the job just got harder.
It's likely I'm not qualified for the job in the first place.
>Ori_B tried to build rc for unix, failed and i conclused it was broken
>and removed the files, assuming anyone who wants rc for windows or
>unix knows where (not) to find it :)
Which UNIX? I get the criteria you outline below, but this seems like a convenient excuse. :)
>just like with drawterm, i'm not going to maintain unix and window
>shit in the 9front tree. it just leads to unmaintained broken shit
>that makes changes harder as i have to do changes in files that i
>can not build to test...
How do you build UNIX and Windows drawterm to test?
sl
next prev parent reply other threads:[~2016-05-18 0:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 1:31 stanley lieber
2016-05-17 1:55 ` [9front] " cinap_lenrek
2016-05-18 0:42 ` stanley lieber [this message]
2016-05-18 6:45 ` cinap_lenrek
2016-05-18 14:48 ` stanley lieber
2016-05-18 15:21 ` hiro
2016-05-18 15:34 ` cinap_lenrek
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=449FF310-DCE6-4FC2-9DC4-3A54B8896C09@stanleylieber.com \
--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).