lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Don't hardcode a limited set of markup signatures. (issue969046)


From: David Kastrup
Subject: Re: Don't hardcode a limited set of markup signatures. (issue969046)
Date: Sun, 13 Jun 2010 21:44:49 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

Reinhold Kainhofer <address@hidden> writes:

> Am Mittwoch, 19. Mai 2010, um 11:42:59 schrieb David Kastrup:
>> Han-Wen Nienhuys <address@hidden> writes:
>> > On Mon, May 3, 2010 at 4:22 AM, David Kastrup <address@hidden> wrote:
>> >> Nice touch, but it's not your work going in the bin.
>> > 
>> > Just for the record: I am ok with the current form of the patch.
>> 
>> As you can see by now, that does not change a thing.  As long as the
>> patch is not in the comfort zone (and that concerns more the patch area
>> than its quality by now) of others with commit privileges, nobody is
>> going to take the responsibility.
>
> Can't we finally give commit access to David? 

That has been done already recently.  It's not likely something that
anybody feels particularly happy about, but it seems like the best way
to reduce friction between my and others' priorities and thresholds of
frustration.

On the plus side, should a contributor post regular git patch sets on
the developer list, I'd have what it takes to commit/merge them as a
regular patch set easily rather than one humongous commit, if consensus
can be reached.

So maybe the net positive effect might be more than just saving people
from some of the uglier outbursts of my frustration.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]