public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds)
Date: Thu, 6 Dec 2012 17:04:58 +0100	[thread overview]
Message-ID: <20121206160458.22993.qmail@stuge.se> (raw)
In-Reply-To: <50C0BFB1.6050407@gentoo.org>

Ian Stakenvicius wrote:
> Essentially, if the problem is with the ebuild or the way the package
> is integrated into gentoo, then fixing it immediately is fine.  If the
> problem is with the software itself, then usually upstream needs to be
> involved before the fix will occur in gentoo.

Yes that's fair of course. None of the handful issues I've had so far
while building 900 packages were about upstream however.


> Also, Emailing patches to the maintainer is much less
> acceptable/desirable than filing them through bugzilla.  As a
> developer, I find it much easier to grab patches from this nice
> centralized bug-tracking filing system than to have to organize them
> in email, and git integration is not something I see changing this.

Have you tried gerrit? It is really a leap ahead.


//Peter


  reply	other threads:[~2012-12-06 16:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-02 15:21 [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-02 15:38 ` Rich Freeman
2012-12-02 19:30   ` Markos Chandras
2012-12-04  1:18     ` Ben de Groot
2012-12-04  7:43       ` Ian Whyman
2012-12-04  9:19       ` Markos Chandras
2012-12-04 15:42         ` Alec Warner
2012-12-04 18:54           ` Markos Chandras
2012-12-06 10:53         ` Ben de Groot
2012-12-04  8:10 ` Rick "Zero_Chaos" Farina
2012-12-04  9:23   ` Markos Chandras
2012-12-04 16:01     ` Rick "Zero_Chaos" Farina
2012-12-04 17:06       ` Proxy maintainers in metadata.xml (was Re: [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds) Diego Elio Pettenò
2012-12-04 17:28         ` Rick "Zero_Chaos" Farina
2012-12-04 18:35           ` Sergey Popov
2012-12-04 18:48             ` Diego Elio Pettenò
2012-12-04 18:51           ` Markos Chandras
2012-12-06 11:02             ` Ben de Groot
2012-12-06 13:28               ` Markos Chandras
2012-12-06 15:27                 ` Peter Stuge
2012-12-06 15:54                   ` Ian Stakenvicius
2012-12-06 16:04                     ` Peter Stuge [this message]
2012-12-06 19:07                   ` Markos Chandras
2012-12-08 17:48             ` Jeroen Roovers
2012-12-04 17:01   ` [gentoo-dev] introduce a soft-limit policy for changing other developers ebuilds hasufell
2012-12-04 17:17     ` Rick "Zero_Chaos" Farina
2012-12-04 17:32       ` hasufell
2012-12-04 17:46         ` Rick "Zero_Chaos" Farina
2012-12-04 18:17           ` hasufell

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=20121206160458.22993.qmail@stuge.se \
    --to=peter@stuge.se \
    --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