public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Developers, please work on underlinking issues!
Date: Fri, 19 Aug 2016 14:46:48 +0200	[thread overview]
Message-ID: <20160819144648.217a5462@portable> (raw)
In-Reply-To: <20160819065844.0463ff8d.mgorny@gentoo.org>

On Fri, 19 Aug 2016 06:58:44 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> On Thu, 18 Aug 2016 15:21:16 +0200
> Alexis Ballier <aballier@gentoo.org> wrote:
> 
> > On Thu, 18 Aug 2016 08:13:14 -0400
> > Rich Freeman <rich0@gentoo.org> wrote:
> >   
> > > If you just check your packages occassionally to make sure they
> > > build with gold it completely achieves the goal, and it will
> > > actually result in fewer bugs using the non-gold linker as
> > > well.    
> > 
> > That's what a tinderbox is for. The only QA problem I see here is
> > that QA doesn't automate that kind of checks anymore since Diego
> > left. Maybe QA should ask Toralf to run a ld.gold tinderbox and
> > avoid asking people to randomly test random packages ?  
> 
> Yes, tinderboxing makes a lot of sense if the bugs are afterwards
> ignored by package maintainers.

"ignored" is rather strong here; considering people join gentoo and
basically work for free, I'd rather say "not considered important
enough" which yields basically the same result but without accusing
people of refusing to fix a bug. With that in mind, everybody is free
to submit patches to bugzie, and if it is a QA goal, QA is free to
apply it after some time. Nothing is blocked here, expect when people
prefer to hit fellow developers "with a cluebat" rather than getting
things done.

> Or in the best case, the maintainer
> tells reporter (Toralf) to file the bug upstream.

It's not because Toralf reported it that he is the only one that has
the right to report it upstream. Obtaining fixes from those that know
the package best is good, isn't it ? I thought we learned from the past
and tried to avoid, e.g., fixing valgrind warnings in libssl by our
own :)

Alexis.


      parent reply	other threads:[~2016-08-19 12:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 20:37 [gentoo-dev] Developers, please work on underlinking issues! Michał Górny
2016-08-17 21:02 ` Ulrich Mueller
2016-08-18  5:39 ` Daniel Campbell
2016-08-18 10:26   ` Alexis Ballier
2016-08-18 12:12   ` Rich Freeman
2016-08-18 10:43 ` Andrew Savchenko
2016-08-18 11:47   ` Lars Wendler
2016-08-18 12:13     ` Rich Freeman
2016-08-18 13:21       ` Alexis Ballier
2016-08-18 21:20         ` Daniel Campbell
2016-08-18 21:56           ` Alexis Ballier
2016-08-18 23:49             ` Mart Raudsepp
2016-08-19  4:58         ` Michał Górny
2016-08-19  7:49           ` Rich Freeman
2016-08-19 15:18             ` james
2016-08-19 12:46           ` Alexis Ballier [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160819144648.217a5462@portable \
    --to=aballier@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