From: Dmitry Gutov <dgutov@yandex.ru>
To: emacs-devel@gnu.org
Subject: Re: Seeking a "Patch Champion"
Date: Mon, 25 Apr 2016 22:50:03 +0300 [thread overview]
Message-ID: <6e404ca5-c10d-396e-d52a-81d7ea3d5ab3@yandex.ru> (raw)
In-Reply-To: <m2eg9wt2i9.fsf@newartisans.com>
On 04/24/2016 12:54 AM, John Wiegley wrote:
> At the present time, I have no way of automating the connection between the
> debbugs tracker and the patchwork server. It *could* be done, using the
> pwclient utility on the debbugs server to close related issues, but I'm afraid
> it's not a switch I can turn on today. :(
I think it should help a lot. But there's no big hurry.
>> Could they be grouped somehow? Most of the time, the next patch submitted to
>> a bug report supersedes the previous one.
>
> I haven't seen any way to do that yet, and it might not be true that there is
> always exactly one patch per bug that is the correct one. For now, determining
> this will be a job of the patch worker.
What I had in mind is more advanced systems like Gerrit where patch
submitters work with patchsets directly and can indicate whether a new
one replaces the old one (that happens somewhat automatically because of
the workflow: you post the new patch as the successor of the old one
because you want to preserve continuity and see the previous comments in
one history with the comments to the current iteration).
Maybe the simplicity of Patchwork will turn out all right. We'll have to
see.
> Btw, glibc apparently uses Patchwork as well. They've even documented their
> workflow with it:
>
> https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow
Looks fine, but it also shows the simplicity of what's provided: it's a
repository of patches where we double-check that no patch has gone
without a second look. And that's it.
We can't comment on them there (i.e. review), or apply with a click of a
button.
next prev parent reply other threads:[~2016-04-25 19:50 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 [this message]
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
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=6e404ca5-c10d-396e-d52a-81d7ea3d5ab3@yandex.ru \
--to=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).