From: Johnny Richard <johnny@johnnyrichard.com>
To: Carlos Maniero <carlos@maniero.me>
Cc: ~johnnyrichard/olang-devel@lists.sr.ht
Subject: Re: [PATCH olang v2] docs: add HACKING documentation
Date: Sat, 17 Feb 2024 21:45:40 +0100 [thread overview]
Message-ID: <k2ixd2sx3e2njaxebqjl4otn4xcqfodciby7k6axrn3qm5k2yd@llfx5tf2uvzy> (raw)
In-Reply-To: <20240217184026.3363538-1-carlos@maniero.me>
Thanks! applied.
To git.sr.ht:~johnnyrichard/olang
5360b26..1c6e4e4 main -> main
prev parent reply other threads:[~2024-02-17 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 18:40 Carlos Maniero
2024-02-17 18:45 ` [olang/patches/.build.yml] build success builds.sr.ht
2024-02-17 20:45 ` Johnny Richard [this message]
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=k2ixd2sx3e2njaxebqjl4otn4xcqfodciby7k6axrn3qm5k2yd@llfx5tf2uvzy \
--to=johnny@johnnyrichard.com \
--cc=carlos@maniero.me \
--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