From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: GID/UID assignment for OpenDKIM (334)
Date: Sat, 05 Oct 2019 19:34:38 +0200 [thread overview]
Message-ID: <cf1349075679831ed9f1f9bb498279cd4a1fda80.camel@gentoo.org> (raw)
In-Reply-To: <87tv8nqeqn.fsf@wedjat.horus-it.com>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
On Sat, 2019-10-05 at 19:33 +0200, Ralph Seichter wrote:
> * Ralph Seichter:
>
> > I'd like to reserve GID/UID 334 for mail-filter/opendkim (see QA bug
> > #694638).
>
> GID/UID 334 is already taken for OpenDKIM, even though the list has
> unfortunately not yet been updated.
Submit a pull request to api-gentoo-org ;-).
>
> See https://archives.gentoo.org/gentoo-dev/message/6de44bcdfb6766fedddc45eede347e0c
> and https://github.com/gentoo/gentoo/pull/13029 .
>
> -Ralph
>
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2019-10-05 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 13:57 [gentoo-dev] RFC: GID/UID assignment for OpenDKIM (334) Ralph Seichter
2019-10-05 17:33 ` Ralph Seichter
2019-10-05 17:34 ` Michał Górny [this message]
2019-10-05 17:43 ` Ralph Seichter
2019-10-05 17:45 ` Ralph Seichter
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=cf1349075679831ed9f1f9bb498279cd4a1fda80.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox