public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages
Date: Mon, 7 Dec 2015 21:19:51 -0500	[thread overview]
Message-ID: <56663E47.20902@gentoo.org> (raw)
In-Reply-To: <CAGfcS_nMGyAf1qHt9K=wC=rjEjiiNR7ebeMryuabgNrUzi0Aiw@mail.gmail.com>

On 12/7/15 7:27 PM, Rich Freeman wrote:
> On Mon, Dec 7, 2015 at 7:05 PM, Alec Warner <antarus@gentoo.org> wrote:
>> 2) Unclear ownership of the problem. One guy makes a commit, 100 packages
>> break. Who is responsible? Its really murky. This is really the toughest
>> problem to me.
> It isn't murky at all.  Nobody should ever commit something that
> simply breaks something else.  Sometimes it is unforseen, and that
> might be ok if it is rare, but the committer can still go and revert
> their commit and sort things out.

Does that include stuff that breaks on systems using musl instead of
glibc?  Or uclibc?  or eudev instead of udev.  What about openrc vs
systemd?  Shall I go on?  Of course its murky.  If you disagree, I'll be
more than happy to pull out dozens of emails where people object when
their stuff breaks other people's stuff with the infamous "why should we
support that shit?"

Anyhow, if the emails are easily filter or have an easy out, I see no
problem.  Murky or not.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA



  reply	other threads:[~2015-12-08  2:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 14:36 [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages Michał Górny
2015-12-06 14:54 ` Dirkjan Ochtman
2015-12-06 15:31 ` Michael Orlitzky
2015-12-06 16:00   ` Michał Górny
2015-12-06 16:09     ` Michael Orlitzky
2015-12-06 16:49       ` Michał Górny
2015-12-06 17:25         ` Michael Orlitzky
2015-12-06 17:49         ` Andreas K. Huettel
2015-12-08  7:01           ` Michał Górny
2015-12-06 16:52       ` Rich Freeman
2015-12-06 17:26         ` Ian Stakenvicius
2015-12-06 18:58           ` Rich Freeman
2015-12-08  0:05 ` Alec Warner
2015-12-08  0:27   ` Rich Freeman
2015-12-08  2:19     ` Anthony G. Basile [this message]
2015-12-08  3:21       ` Rich Freeman
2015-12-08  6:59   ` Michał Górny
2015-12-08 19:11 ` Daniel Campbell

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=56663E47.20902@gentoo.org \
    --to=blueness@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