all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH v1] Let input queue deal gracefully with up-events
Date: Thu, 05 Feb 2015 20:27:15 +0100	[thread overview]
Message-ID: <87vbjgxip8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvd25o41iy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 05 Feb 2015 14:11:46 -0500")

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.

In fact, you explicitly recommended this way of operation in
<URL:http://lists.gnu.org/archive/html/emacs-devel/2015-01/msg01065.html>.
On the other hand, this list has recently seen considerable rebuke
against a developer doing exactly that.  I am not interested in the role
of a black sheep so I prefer using the submission paths intended for
untrusted developers.

> Then you'd just have to wait for David to install your patch,

As long as he cannot be trusted to act responsibly and not commit
patches that need others to clean up after him, I cannot see it as
desirable to grant him push access.

He has been judged in clear need of vetting, and the tool for that are
the mailing list and the bug tracker.

-- 
David Kastrup



  reply	other threads:[~2015-02-05 19:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 13:31 [PATCH] Let input queue deal gracefully with up-events David Kastrup
2015-01-28 14:58 ` Alan Mackenzie
2015-01-28 15:19   ` [PATCH v1] " David Kastrup
2015-02-05 17:23     ` David Kastrup
2015-02-05 19:11       ` Stefan Monnier
2015-02-05 19:27         ` David Kastrup [this message]
2015-02-05 21:07           ` Ivan Shmakov
2015-02-05 21:42             ` David Kastrup
2015-02-05 19:17       ` Ivan Shmakov
2015-01-28 19:35 ` [PATCH] " Stefan Monnier
2015-01-28 19:50   ` David Kastrup
2015-01-28 22:14     ` Stefan Monnier
2015-01-28 22:55       ` David Kastrup
2015-01-28 22:19 ` Stefan Monnier
2015-01-28 23:06   ` David Kastrup
2015-01-29  3:57     ` Stefan Monnier
2015-01-29  8:49       ` David Kastrup
2015-01-29 15:00         ` Stefan Monnier
2015-01-29 15:14           ` David Kastrup

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=87vbjgxip8.fsf@fencepost.gnu.org \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.