From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: repo/gentoo.git, or how committing is challenging
Date: Tue, 22 Dec 2015 09:04:10 -0500 [thread overview]
Message-ID: <CAGfcS_ms1f_U+magCguUCnNQmAzrp-+ZM62hMH5=O-Q=n_5G_w@mail.gmail.com> (raw)
In-Reply-To: <567950CB.4070307@gentoo.org>
On Tue, Dec 22, 2015 at 8:31 AM, Patrick Lauer <patrick@gentoo.org> wrote:
>>
>> Do you want to see this fixed?
>> Are you willing to do the fixing yourself?
> I don't have infinite time, and wasting a day documenting things that
> should have been documented a year ago is not a good way of spending time.
So, it sounds like the answer to the first question is yes, and the
second is no...
>>
>> If the answer to the first question is yes, and the second is no, then
>> you've just volunteered for the job of either community motivator, or
>> frustrated user. The goal then is to make people care more about
>> going out of their way to fix things than going out of their way to
>> find ways to make you even more frustrated. Which do you think is
>> going to be more emotionally satisfying to those who read this thread?
>>
> Things working.
>
> So, the trick is not to have user-visible breakage.
>
> Now you know the great trick too and can apply it to your daily life.
>
Yeah, but if I don't lift a finger to help fix this bug, I know it
will drive you crazy for a few more days, or even months. That's
basically my point. You're basically begging everybody who would
otherwise want to fix this issue to just troll you instead. And that
isn't helpful to anybody.
You can't just wave your hands and have no user-visible breakage. You
either need to fix things yourself or help motivate others to do it.
The approach you're taking is about as helpful as telling your
significant other that they're fat. After they're finished stabbing
you to death with their spoon they're going to stick it in some Ben
and Jerry's.
Ugh, gotta take a break. Happy holidays!
--
Rich
next prev parent reply other threads:[~2015-12-22 14:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 17:36 [gentoo-dev] repo/gentoo.git, or how committing is challenging Patrick Lauer
2015-12-13 17:38 ` Patrick Lauer
2015-12-13 18:50 ` Andrew Savchenko
2015-12-13 19:05 ` Patrick Lauer
2015-12-13 19:20 ` Andrew Savchenko
2015-12-13 21:30 ` Mike Gilbert
2015-12-13 21:53 ` Andrew Savchenko
2015-12-14 3:00 ` Brian Dolbec
2015-12-14 6:23 ` Daniel Campbell
2015-12-14 11:12 ` Patrick Lauer
2015-12-14 17:52 ` Mike Gilbert
2015-12-15 0:31 ` Peter Stuge
2015-12-21 3:21 ` [gentoo-dev] " Ryan Hill
2015-12-21 18:59 ` Peter Stuge
2015-12-22 0:45 ` Rich Freeman
2015-12-22 9:41 ` Patrick Lauer
2015-12-22 12:08 ` Rich Freeman
2015-12-22 12:53 ` Patrick Lauer
2015-12-22 13:14 ` Rich Freeman
2015-12-22 13:31 ` Patrick Lauer
2015-12-22 14:04 ` Rich Freeman [this message]
2015-12-22 18:21 ` Patrick Lauer
2015-12-22 23:55 ` Peter Stuge
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='CAGfcS_ms1f_U+magCguUCnNQmAzrp-+ZM62hMH5=O-Q=n_5G_w@mail.gmail.com' \
--to=rich0@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