From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Brett Gilio <brettg@gnu.org>
Cc: 42447@debbugs.gnu.org
Subject: bug#42447: Issue with CGIT service
Date: Mon, 27 Jul 2020 13:24:38 +0200 [thread overview]
Message-ID: <20200727112438.aitj3tb26g43ednd@pelzflorian.localdomain> (raw)
In-Reply-To: <20200727111811.dspglgbldmuru3l6@pelzflorian.localdomain>
On Mon, Jul 27, 2020 at 01:18:19PM +0200, pelzflorian (Florian Pelz) wrote:
> Perhaps this can be properly fixed by using supplementary groups now
> that <https://issues.guix.info/issue/41573> has been pushed.
P.S. I had thought of <https://issues.guix.info/issue/38438> where
fcgiwrap is involved.
prev parent reply other threads:[~2020-07-27 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 19:30 bug#42447: Issue with CGIT service Brett Gilio
2020-07-27 10:53 ` Ludovic Courtès
2020-07-27 11:18 ` pelzflorian (Florian Pelz)
2020-07-27 11:24 ` pelzflorian (Florian Pelz) [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
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=20200727112438.aitj3tb26g43ednd@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=42447@debbugs.gnu.org \
--cc=brettg@gnu.org \
/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.savannah.gnu.org/cgit/guix.git
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).