From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: andreas.roehler@online.de, emacs-devel@gnu.org
Subject: Re: Seeking a "Patch Champion"
Date: Wed, 27 Apr 2016 09:16:50 +0300 [thread overview]
Message-ID: <83inz3zict.fsf@gnu.org> (raw)
In-Reply-To: <baaedb30-5f78-630c-8894-2bb21c792c4b@yandex.ru> (message from Dmitry Gutov on Tue, 26 Apr 2016 23:24:20 +0300)
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 26 Apr 2016 23:24:20 +0300
>
> I may simply have a narrow-ish area of interest, though. The kind of
> patches that might fall through the crash are likely targeting an area
> without an active maintainer.
>
> An active patch herder might manage those in Patchwork, but as long as
> they are submitted to the bug tracker, they won't be lost (even if no
> one is actively reviewing them).
I think a more useful approach is to try to handle any patch which you
understand well enough to feel it's about right. (The cracks between
the areas of our interest are too wide to only handle those within the
areas.) That still would leave a lot of doubt about whether a patch
could do any harm in some other place or use case; I wonder if we
could come up with some procedure to minimize that chance.
next prev parent reply other threads:[~2016-04-27 6:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 21:22 Seeking a "Patch Champion" John Wiegley
2016-04-23 21:45 ` Dmitry Gutov
2016-04-23 21:54 ` John Wiegley
2016-04-25 19:50 ` Dmitry Gutov
2016-04-25 19:59 ` Dmitry Gutov
2016-04-25 21:29 ` John Wiegley
2016-04-25 21:35 ` Dmitry Gutov
2016-04-26 14:27 ` John Wiegley
2016-04-25 11:29 ` Nicolas Petton
2016-04-25 17:37 ` John Wiegley
2016-04-25 18:48 ` Nicolas Petton
2016-04-25 19:17 ` John Wiegley
2016-04-25 19:28 ` John Wiegley
2016-04-25 16:40 ` Lars Magne Ingebrigtsen
2016-04-25 18:11 ` Karl Fogel
2016-04-25 18:14 ` Lars Magne Ingebrigtsen
2016-04-25 19:22 ` Karl Fogel
2016-04-25 19:51 ` Dmitry Gutov
2016-04-25 20:27 ` Dmitry Gutov
2016-04-25 20:37 ` Lars Magne Ingebrigtsen
2016-04-25 20:51 ` Dmitry Gutov
2016-04-25 21:14 ` Lars Magne Ingebrigtsen
2016-04-25 21:34 ` John Wiegley
2016-04-25 22:04 ` Lars Magne Ingebrigtsen
2016-04-25 23:44 ` Lars Magne Ingebrigtsen
2016-04-26 6:32 ` Andreas Röhler
2016-04-26 14:30 ` John Wiegley
2016-04-26 15:04 ` Nicolas Petton
2016-04-26 20:24 ` Dmitry Gutov
2016-04-26 21:01 ` John Wiegley
2016-04-27 6:16 ` Eli Zaretskii [this message]
2016-04-27 14:40 ` Lars Magne Ingebrigtsen
2016-04-27 15:31 ` Nicolas Petton
2016-04-27 15:49 ` Lars Ingebrigtsen
2016-05-02 7:55 ` Nicolas Petton
2016-05-02 20:55 ` John Wiegley
2016-05-02 21:54 ` Lars Ingebrigtsen
2016-05-03 7:58 ` Michael Albinus
2016-04-28 19:30 ` Philipp Stephani
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83inz3zict.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andreas.roehler@online.de \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).