From: EuAndreh <eu@euandre.org>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: Can't serve a custom channel on a HTTPS repository
Date: Tue, 24 Aug 2021 13:13:55 -0300 [thread overview]
Message-ID: <162982163567.793927.6624373973993891167@localhost> (raw)
In-Reply-To: <162904717504.1902474.2861575348138623741@localhost>
FYI, I did send a message to the mailing list. I'm waiting on an answer, and
I'll try to make the possible solution more broadly available, if a can end up
with one.
https://lists.gnu.org/r/savannah-hackers-public/2021-08/msg00000.html
next prev parent reply other threads:[~2021-08-24 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 17:36 Can't serve a custom channel on a HTTPS repository EuAndreh
2021-07-26 22:37 ` divoplade
2021-07-27 0:15 ` EuAndreh
2021-07-30 14:59 ` EuAndreh
2021-08-04 1:54 ` EuAndreh
2021-07-27 15:22 ` Leo Famulari
2021-08-08 17:49 ` EuAndreh
2021-08-08 22:21 ` Leo Famulari
2021-08-09 13:41 ` EuAndreh
2021-08-09 16:35 ` Leo Famulari
2021-08-15 17:06 ` EuAndreh
2021-08-24 16:13 ` EuAndreh [this message]
2021-09-15 17:00 ` EuAndreh
2021-09-15 17:34 ` EuAndreh
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162982163567.793927.6624373973993891167@localhost \
--to=eu@euandre.org \
--cc=help-guix@gnu.org \
--cc=leo@famulari.name \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).