Re: Recording the current branch on each commit?

From: David Kastrup <dak@gnu.org>
Date: Apr 29, 2014, 09:47 UTC
Message-ID: <87mwf431t3.fsf@fencepost.gnu.org>
In-Reply-To: <535f702352d21_3aee3b2f0b9@nysa.notmuch>

Felipe Contreras <felipe.contreras@gmail.com> writes:

Show 18 quoted lines

> David Kastrup wrote:
>
>> Even while the ones getting the benefits from your work will not
>> feel an obligation to make it worth your while, there is a
>> difference in satisfaction between getting your work trashed and
>> getting it used.
>
> I don't know why this keeps poping up in the thread, but it is
> starting to seem to me that you are under the impression that I'm
> somehow unable to get my patches merged.
>
> Look at the list of contributors of the past year, see who is #2:
>
> https://www.ohloh.net/p/git/contributors?query=&sort=commits_12_mo
>
> I know what kind of patches can get in, and what patches can't (the
> ones that do any kind of relevant change). I know that from
> experience.

Well, there you have it. The ones that do any kind of relevant change are the ones that need thinking about and consideration. And when you are so verbose about them that

a) you are getting on people's nerves b) nobody else finds something worth saying that you did not already say

then the net effect is that it feels to the person in question he's mainly doing you (and not all that many others) a favor by investing the work for properly considering it and its consequences.

Which is not much of an incentive. At any rate, we are in a phase supposed to be shortly before the release of 2.0. So it is actually quite by design that patches doing any kind of relevant changes are not currently going through. You can be as nice or ugly about it as you want right now and it will not affect 2.0 any more.

But it might do so regarding 2.1.

-- 
David Kastrup