unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: Seeking a "Patch Champion"
Date: Mon, 25 Apr 2016 23:27:37 +0300	[thread overview]
Message-ID: <211814b3-3aeb-9dfb-117c-0459847dd1fc@yandex.ru> (raw)
In-Reply-To: <m3k2jlej68.fsf@gnus.org>

On 04/25/2016 07:40 PM, Lars Magne Ingebrigtsen wrote:

> I'm afraid I don't think this is likely to help much.  Since it's not
> hooked up to the bug tracker, the list of patches on that site will just
> grow increasingly outdated.  Having somebody herd a patch after it's
> already been applied is a waste of everybody's time.
>
> And I don't think adding yet another formality to the already pretty
> complicated "apply this patch already" "work flow" (for want of a better
> word) is the way to go.

I'm inclined to agree.

> But the lost patch situation in Emacs is a genuine problem, and one that
> I think may be disencouraging new contributors.  Here's what I think
> should happen:

I don't know if it is: I've just went through the lists, and didn't find 
a single patch within my area of interest that had "fallen through the 
cracks". So I basically had to go and sort all of them into Accepted, 
RFC and Rejected. And several belonging to the issues where the 
discussions hadn't come to the conclusion yet (those I've left untouched).

> 1) Whenever somebody posts a patch to emacs-devel, and you don't feel
> like applying it at once, tell them "send this via `M-x
> report-emacs-bug', otherwise it'll never be applied".

This seems to work well enough. Until we have evidence to the contrary, 
the ability to show bugs with patches in debbugs should be sufficient, I 
think.

Or maybe Patchwork will help other contributors better, I don't know.

If we had switched to a better bug tracker, on the other hand... :)



  parent reply	other threads:[~2016-04-25 20:27 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 [this message]
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
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=211814b3-3aeb-9dfb-117c-0459847dd1fc@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).