From: "Carlos Maniero" <carlos@maniero.me>
To: "Carlos Maniero" <carlos@maniero.me>,
"Johnny Richard" <johnny@johnnyrichard.com>
Cc: <~johnnyrichard/olang-devel@lists.sr.ht>
Subject: Re: [RFC] Namespaces in OLANG
Date: Sun, 07 Apr 2024 17:58:45 -0300 [thread overview]
Message-ID: <D0E6XB0HJ8ET.1QG9HPVR5LEES@maniero.me> (raw)
In-Reply-To: <D0E6Q0JNP8OM.1Q44XUB3YVN7V@maniero.me>
> So if you don't get it I believe we could just
> drop it.
Let me try to fix my tone here! I was ruge.
I mean, If we could not agree, I think we could drop it and try to
discuss it later in the future.
I confess I started to fell offended by you named the solution complex
where IMO it is pretty simple actually.
next prev parent reply other threads:[~2024-04-07 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 2:46 Carlos Maniero
2024-03-27 18:39 ` Johnny Richard
2024-03-28 13:41 ` Carlos Maniero
2024-04-06 16:51 ` Johnny Richard
2024-04-07 20:49 ` Carlos Maniero
2024-04-07 20:58 ` Carlos Maniero [this message]
2024-04-08 2:45 ` Carlos Maniero
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=D0E6XB0HJ8ET.1QG9HPVR5LEES@maniero.me \
--to=carlos@maniero.me \
--cc=johnny@johnnyrichard.com \
--cc=~johnnyrichard/olang-devel@lists.sr.ht \
/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.
Code repositories for project(s) associated with this public inbox
https://git.johnnyrichard.com/olang.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox