From: bkiziuk <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] Re: [tohojo/flent] --remote-host doesn't seem to work correctly (#222)
Date: Tue, 16 Mar 2021 09:59:57 -0700 [thread overview]
Message-ID: <tohojo/flent/issue/222/issue_event/4465809275@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/222@github.com>
[-- Attachment #1: Type: text/plain, Size: 194 bytes --]
Closed #222.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/222#event-4465809275
[-- Attachment #2: Type: text/html, Size: 1432 bytes --]
next prev parent reply other threads:[~2021-03-16 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 16:37 [Flent-users] " bkiziuk
2021-03-15 23:32 ` [Flent-users] " Toke Høiland-Jørgensen
2021-03-16 16:59 ` bkiziuk
2021-03-16 16:59 ` bkiziuk [this message]
2021-03-16 17:14 ` Toke Høiland-Jørgensen
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
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/issue/222/issue_event/4465809275@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJPZABFTOZC5WRCPKD756LTCQ3EVBNHHDDCY5IU@reply.github.com \
--cc=subscribed@noreply.github.com \
--subject='[Flent-users] Re: [tohojo/flent] --remote-host doesn'\''t seem to work correctly (#222)' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox