From: ori@eigenstate.org
To: plan9fullfrontal@qs.co.nz, 9front@9front.org
Subject: Re: [9front] Unsolicited patch for tclsh amd64
Date: Tue, 24 Mar 2020 16:39:21 -0700 [thread overview]
Message-ID: <DC4750E5B93678F4304FCFFE805C8348@eigenstate.org> (raw)
In-Reply-To: <83a6d4e6-e3af-7c6a-821a-8222c58c91b7@qs.co.nz>
> It might surprise you to know that, I dont give a fuck what you think.
>
> Ori only fixed a problem (or maybe he has not fixed anything) because I
> investigated a problem and diagnosed a cause.
>
> Unfortunately I have moved on from working on tcl problems and onto the
> application I want to develop, hence the comments attached to the
> aforementioned email.
>
> As the email stated, 'Its unofficial and a kludge', maybe someone just
> wants to use tcl and get on with their life (as I do).
>
> I did not ask you to take note of the patch and stated clearly that it
> was a means to and end and I expected people to ignore what they are not
> interested in, If this is a private club, then I am ok with leaving you
> to it, just let me know.
>
>
>
> On 03/25/2020 07:26 AM, cinap_lenrek@felloff.net wrote:
>> no. ape should be fixed instead. we dont want to have hacks upon hacks.
>>
>> ori is working on it.
>>
>> --
>> cinap
>
> --
> We need another plan
relax. we all agree that this was the wrong way to fix it, so
I put a patch in.
sizeof(ptrdiff_t) is now 8, since it'll probably unconfuse other
applications, and you can back out the ptrdiff_t stuff at your
leisure.
thanks for tracking down the issues.
next prev parent reply other threads:[~2020-03-24 23:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 7:56 Trevor Higgins
2020-03-22 20:52 ` [9front] " ori
2020-03-24 18:26 ` cinap_lenrek
2020-03-24 23:02 ` Trevor Higgins
2020-03-24 23:39 ` ori [this message]
2020-03-25 12:33 ` hiro
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=DC4750E5B93678F4304FCFFE805C8348@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=plan9fullfrontal@qs.co.nz \
/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).