Re: [PATCH v1] Let input queue deal gracefully with up-events

[Ivan Shmakov <ivan@siamics.net>]

>>>>> David Kastrup <dak@gnu.org> writes:
>>>>> Stefan Monnier <monnier@IRO.UMontreal.CA> writes:

 >>> <URL:http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19746>.  Judging
 >>> from the number of wishlist items in the tracker including a patch,
 >>> that does not appear to increase its chances of getting applied but
 >>> at least it is then rotting in the proper place.

 >> What would increase the chances, would be you requesting
 >> write-access, of course ;-)

 > Basically you say that the patch submission and vetting process is
 > fundamentally broken and useless and that people should ignore the
 > developer list and bug tracker and just dump their code into the
 > repository instead and see whether others want to fix it.

	I’m unsure if this comment of mine will help or not, but I /do/
	see the difference between “the change is OK and I will install
	the patch” and “the change is OK, but I will /not/ install the
	patch (because of…)” as the outcomes of the review process.

	In this particular case, the review process (AIUI) resulted in
	the latter, due to the disagreement on the wording of a single
	comment in the code.  However, given the “the change is OK”
	part, I see no reason for an interested party to refrain from
	pushing the change, either simply changing that single line of
	contention (so to say) him- or herself along the way, – or
	leaving it to the party interested in /that/ change.

	Should the review process result in the “the change is NOT OK”
	outcome, it would indeed be inappropriate for a developer to
	push the change.  But that’s not the case for #19746.

[…]

-- 
FSF associate member #7257  http://boycottsystemd.org/  … 3013 B6A0 230E 334A