public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michal Prívozník" <mprivozn@redhat.com>
To: gentoo-dev@lists.gentoo.org, Michael Orlitzky <mjo@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] app-emulation/libvirt-snmp: version bump to 0.0.4
Date: Sat, 27 Oct 2018 12:16:26 +0100	[thread overview]
Message-ID: <2c0e94db-bfde-a8ee-2eb5-26027fa9a56c@redhat.com> (raw)
In-Reply-To: <fb2f5e53-181c-3780-8e24-882cd30f1017@gentoo.org>

On 10/26/2018 05:42 PM, Michael Orlitzky wrote:
> On 10/26/2018 04:40 AM, Michal Prívozník wrote:
>>
>> So the desired way is to use github pull requests? That is rather
>> unfortunate. 
> 
> In this case there's no "project" associated with libvirt-snmp; but if
> there were, it would have a <project-name>@gentoo.org alias that you
> could send patches to. 

Well, why don't we create something like virtualization@gentoo.org? That
would be a mailing list to discuss virtualization related topics.

Bugzilla is still the official (and in this case,
> best) place to put these in my opinion.

I don't think so. I've been attaching patches to BZ in the past and the
response time was very poor. I know everybody is working on gentoo in
their spare time and I appreciate it, but why not use something that
works for both sides? I think that if we want to attract more volunteers
we have to have a process that goes the least into their way.

> 
> Personally I don't mind them on the -dev list, but they do get sent to a
> thousand people who have no interest in or ability to commit them.
> 

That is the case on every mailing list. Every -dev list has number of
subscribes far bigger than number of people with commit access.

But I respect your decision guys. I am going to stop posting patches
until there's an agreement on how to do that.

Michal


  reply	other threads:[~2018-10-27 11:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-25 15:31 [gentoo-dev] [PATCH] app-emulation/libvirt-snmp: version bump to 0.0.4 Michal Privoznik
2018-10-25 17:59 ` Mikle Kolyada
2018-10-26  1:04   ` Matthias Maier
2018-10-26  5:52     ` Mikle Kolyada
2018-10-26  8:40       ` Michal Prívozník
2018-10-26 16:42         ` Michael Orlitzky
2018-10-27 11:16           ` Michal Prívozník [this message]
2018-10-27 12:18             ` Joonas Niilola
2018-10-27 14:35               ` Fabian Groffen
2018-10-27 16:15                 ` Matthias Maier
2018-10-27 14:45               ` Alec Warner
2018-10-28 16:02               ` William Hubbs
2018-10-25 22:25 ` [gentoo-dev] " Matthias Maier

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=2c0e94db-bfde-a8ee-2eb5-26027fa9a56c@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mjo@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