From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Changes made by acct-* ebuilds
Date: Sun, 16 Feb 2020 07:49:27 +0100 [thread overview]
Message-ID: <c792496b6425707fc84986fd7424ae56f78b19de.camel@gentoo.org> (raw)
In-Reply-To: <20200215223505.763dcd0e@amdahl.home.chead.ca>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Sat, 2020-02-15 at 22:35 -0800, Christopher Head wrote:
> On Thu, 13 Feb 2020 08:09:13 -0800
> Christopher Head <chead@chead.ca> wrote:
>
> > On Wed, 12 Feb 2020 19:14:45 +0100
> > Michał Górny <mgorny@gentoo.org> wrote:
> >
> > > I'm pretty sure user.eclass does print whatever changes it is doing.
> > > It isn't elog-ged though, I admit. This is probably worth fixing.
>
> So, I didn’t intend to provoke a massive debate here—personally I
> somewhat prefer users being modified by new versions of the user
> ebuilds so that I get security fixes as time goes by to fix e.g. users
> being in groups they shouldn’t be, but it’s not a huge deal to me.
>
> elogging when the eclass makes changes, though: Michał, do you want me
> to file a bug at bugs.gentoo.org for that? Or is it trivial enough you
> prefer to just do it straight away and not bother?
I've already sent a patch and it's got no replies, so I guess I'll just
push it today.
--
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:[~2020-02-16 6:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 18:02 [gentoo-dev] Changes made by acct-* ebuilds Christopher Head
2020-02-12 18:11 ` Alec Warner
2020-02-12 18:14 ` Michał Górny
2020-02-13 16:09 ` Christopher Head
2020-02-13 16:17 ` Michał Górny
2020-02-16 6:35 ` Christopher Head
2020-02-16 6:49 ` Michał Górny [this message]
2020-02-13 1:32 ` Thomas Deutschmann
2020-02-13 5:26 ` Christopher Head
2020-02-13 5:59 ` Michał Górny
2020-02-13 7:03 ` Alec Warner
2020-02-13 8:10 ` Michał Górny
2020-02-18 4:57 ` desultory
2020-02-13 16:17 ` Mike Gilbert
2020-02-13 23:24 ` Michael 'veremitz' Everitt
2020-02-14 3:37 ` Mike Gilbert
2020-02-14 14:12 ` Thomas Deutschmann
2020-02-14 14:41 ` Michał Górny
2020-02-14 15:38 ` Mike Gilbert
2020-02-14 17:09 ` Thomas Deutschmann
2020-02-14 17:17 ` Michał Górny
2020-02-14 17:42 ` Thomas Deutschmann
2020-02-14 17:55 ` Michał Górny
2020-02-14 19:48 ` Vadim A. Misbakh-Soloviov
2020-02-14 20:02 ` Vadim A. Misbakh-Soloviov
2020-02-15 1:17 ` Michael 'veremitz' Everitt
2020-02-14 19:05 ` Mike Gilbert
2020-02-14 19:49 ` Rolf Eike Beer
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=c792496b6425707fc84986fd7424ae56f78b19de.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