public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Bugzilla etiquette suggestions
Date: Sun, 12 Feb 2006 23:32:39 +0000	[thread overview]
Message-ID: <43EFC597.7070409@gentoo.org> (raw)
In-Reply-To: <20060212225802.GA11542@cyclops.localdomain>

Marien Zwart wrote:
> I think this is too much effort, especially for small corrections. I
> tend to fix them myself, commit with a message like "...based on an
> ebuild from ... (bug #....)" and comment on the bug like "Committed
> with minor changes". It would probably be a good thing if I went into
> a bit more detail about what the "minor changes" were and why I made
> them, I guess :)

Perhaps you could try this a couple of times when the opportunity next 
arises. If done well, you only need to type a sentence or two if it is 
just minor issues that need correcting. Also bookmark Ciaran's nice mini 
FAQ which covers lots of common mistakes:

http://dev.gentoo.org/~ciaranm/docs/mw-faq

It may feel a little harsh to give someone a canned response just by 
pasting a URL in the comment field, but curious readers will find his 
faq.txt which explains nicely that we aren't evil/lazy, we just have a 
lot of work to do. Thanks Ciaran!

I guess the only other downside to this approach is that it delays the 
fix - instead of fixing it right then, you have to wait for another 
round of communication to complete before closing the bug. That is 
undesirable for people with busy schedules.

Thanks for the feedback.
Daniel
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-02-12 23:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 21:11 [gentoo-dev] Bugzilla etiquette suggestions Daniel Drake
2006-02-12 21:43 ` Henrik Brix Andersen
2006-02-12 23:24   ` Daniel Drake
2006-02-13  0:57     ` Ferris McCormick
2006-02-13  8:09       ` Ciaran McCreesh
2006-02-13  9:50     ` [gentoo-dev] " Duncan
2006-02-13 16:11       ` Daniel Drake
2006-02-13 17:17         ` [gentoo-dev] " Duncan
2006-02-16 11:02       ` [gentoo-dev] " Michael Cummings
2006-02-13 10:51     ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2006-02-13 16:30       ` Daniel Drake
2006-02-12 22:53 ` [gentoo-dev] " Duncan
2006-02-12 23:39   ` Daniel Drake
2006-02-13  8:13   ` Ciaran McCreesh
2006-02-13 17:26     ` Richard Fish
2006-02-14  2:54       ` lnxg33k
2006-02-13 18:39   ` Simon Stelling
2006-02-13 18:49     ` Ciaran McCreesh
2006-02-13 19:00       ` Patrick McLean
2006-02-13 19:06         ` Marien Zwart
2006-02-13 19:07       ` Grobian
2006-02-13 19:21         ` Ciaran McCreesh
2006-02-13 19:29           ` Grobian
2006-02-13 20:02             ` Carsten Lohrke
2006-02-13 20:13               ` Grobian
2006-02-13 19:36       ` Diego 'Flameeyes' Pettenò
2006-02-14 13:03     ` [gentoo-dev] " Duncan
2006-02-14 13:18       ` Stephen P. Becker
2006-02-15  7:48         ` [gentoo-dev] " Duncan
2006-02-12 22:58 ` [gentoo-dev] " Marien Zwart
2006-02-12 23:32   ` Daniel Drake [this message]
2006-02-13  8:16     ` Ciaran McCreesh
2006-02-13 19:12       ` Donnie Berkholz
2006-02-13  4:06 ` Ned Ludd
2006-02-17 14:20   ` Shyam Mani
2006-02-17 14:11 ` Shyam Mani

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=43EFC597.7070409@gentoo.org \
    --to=dsd@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