git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: jidanni@jidanni.org
Cc: johannes.schindelin@gmx.de, tlikonen@iki.fi, nanako3@lavabit.com,
	git@vger.kernel.org
Subject: Re: git maintenance bug tracker sooner better than later
Date: Fri, 06 Feb 2009 13:56:02 +0100	[thread overview]
Message-ID: <498C3362.9080105@op5.se> (raw)
In-Reply-To: <87tz7bniyk.fsf@jidanni.org>

jidanni@jidanni.org wrote:
> Anyway, I have this file
>   -rw-r--r--  1   19561 2009-01-13 03:26 DietCherries17
> where I have 17 tiny documentation patches that sent to
> git@vger.kernel.org but nothing happened.
> Perhaps I could send them to a volunteer who could see if any of them
> are useful and then do something with them. Thanks.

That's really not how things work around here, or on any OSS project
I've ever been engaged in. It's your itch to scratch, so before you
have a chance of getting anyone else to scratch it for you, you have
to either make those others interested enough to volunteer to do it
for you, or you get to scratch away as much as you like yourself.

The longer and more difficult way is to scratch the itches of so
many others that people want to help you out because the chance
you'll do something else which is *also* productive is high enough
to warrant it. So far, you seem more interested in shooting from
the hip, sending patches at random that have little or no impact
on anything and that nobody else is genuinely interested in. That's
fine if you also pick up the pieces of your poor aim and actually
follow through but when it really just causes more work for others
than the end-result would have been worth to start with, the net
result is counter-productive and you have to work harder when you
have ideas/patches that are actually good than you would have been
forced to with a better overall signal-to-noise ratio.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  parent reply	other threads:[~2009-02-06 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 19:07 git maintenance bug tracker sooner better than later jidanni
2009-02-02 22:07 ` Christian MICHON
2009-02-03 10:05 ` Nanako Shiraishi
2009-02-03 13:38   ` Teemu Likonen
2009-02-03 14:42     ` Johannes Schindelin
2009-02-04  0:28       ` jidanni
2009-02-06 12:33         ` Johannes Gilger
2009-02-06 12:56         ` Andreas Ericsson [this message]
2009-02-06 13:24           ` jidanni
2009-02-06 16:30             ` Johannes Gilger

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=498C3362.9080105@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=jidanni@jidanni.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=nanako3@lavabit.com \
    --cc=tlikonen@iki.fi \
    /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;
as well as URLs for NNTP newsgroup(s).