From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Editing RDEPEND without a new revision (again)
Date: Fri, 25 Oct 2019 15:27:42 +1300 [thread overview]
Message-ID: <20191025152742.44c60eaf@katipo2.lan> (raw)
In-Reply-To: <4fa10436-c795-8dd3-c932-75b0a56da503@veremit.xyz>
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Fri, 25 Oct 2019 03:03:26 +0100
Michael Everitt <gentoo@veremit.xyz> wrote:
> Forgive my lack of git-fu, but which commit did this? Can we name & shame
> the author and committer publicly, and in front of QA, so that this kind of
> violation is highlighted to all, and noted for future reference?
I think you can blame zlogene.
I didn't use git-fu, I just searched my email logs of gentoo-commits ;)
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=db5beca3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-25 2:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 22:04 [gentoo-dev] Editing RDEPEND without a new revision (again) Michael Orlitzky
2019-10-25 2:03 ` Michael Everitt
2019-10-25 2:27 ` Kent Fredric [this message]
2019-10-25 13:43 ` Michael Orlitzky
2019-10-25 18:20 ` Michael Everitt
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=20191025152742.44c60eaf@katipo2.lan \
--to=kentnl@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