On Thu, Aug 9, 2012 at 5:54 PM, Junio C Hamano <gits...@pobox.com> wrote:
>>> Forwarding a misdirected patch to the maintainer who is free to pick
>>> or ignore.
>> How am I supposed to know if a patch has been ignored as an oversight
>> (in which case I would resend), or because the maintainer decided not
>> to include it (in which case I would not resend in order to not annoy
>> the maintainer)?
> By hearing from Paul (or asking directly), perhaps?
I did that, in a private mail due to some temporary mailing list
problems, but did not get an answer. So my question was referring to
Paul. How I should know whether Paul ignores my patch due to an
oversight, or because he is not interested? And because of this
ambiguity in ignoring a patch I think an explicit NACK should be
mandatory if a maintainer is not interested in a patch.
> And that goes both ways. If the logo of the "official" site is not
> something so important that git-scm.com can change without gaining
> community consensus first, then it equally is within the editorial
> discretion of individual git package's maintainer to keep using the
> original not the updated logo.
I admit that I was assuming community consensus on the new logo
exactly *because* I saw it on git-scm.com. On the other hand, from my
experience the Git community is not exactly one where is it
particularly easy to get consensus on something, so I completely
understand and support Scott's habit to sometimes go one way without
consulting the community first.
Anyway, I'll include the patch into Git for Windows, because that's
what our users ask for.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html