[patchew-devel] Re: About projects already running on patchew.org
- From: Fam Zheng <famz@xxxxxxxxxx>
- To: Ramon Medeiros <ramonn@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 18 Nov 2016 00:52:50 +0800
On Thu, 11/17 14:22, Ramon Medeiros wrote:
I want to use Patchew for it. My propose with patchew was:
Every patch sent to Kimchi mailing list and subprojects (see wok, ginger and
gingerbase) will be merged in a branch and run make check (unit tests).
As I saw, the merging part is working yet:
http://patchew.org/Kimchi/1479226967-13054-1-git-send-email-archus@xxxxxxxxxxxxxxxxxx/
Yes and no. Patchew currently assumes each mailing list has only one repo, so I
need to know how subprojects are distinguished (e.g. subject prefix [wok]?) in
Kimchi, and then implement a subproject-aware logic. For example:
http://patchew.org/Kimchi/1477404741-17641-1-git-send-email-dhbarboza82@xxxxxxxxx/
An email from patchew will be sent to verify if patch is working or not
Do you think patchew can handle this? I know that patchew has a
customization for adding a script to run tests.
Yes, running tests and sending emails are already supported and we are using it
for qemu:
https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg03409.html
So without waiting for patchew support of subproject, we can already start
testing patches for the main Kimchi repo. To do that you'd need to prepare a
test machine that runs "patchew-cli tester -p Kimchi" which polls patchew server
for newly indexed patches and execute the distributed tests.
Fam
Other related posts:
