search

patchew-project / patchew

A patch email tracking and testing system
MIT License
73 stars 24 forks source link

Subproject support #56

Closed famz closed 6 years ago

famz commented 6 years ago

This is the minimum to handle subprojects. A subproject is basically a separate project but is better managed hierarchically to avoid clutter.

This should make it possible to fix the failed git applies in http://patchew.org/Libvirt/, where patches tagged as python, tck, perl etc. should acutally be applied on top of different git repos, instead of the main one.

famz commented 6 years ago

I'm not sure I understand how there would be no repo/tag/URL, but the patches could still be applied successfully?

patchew-cli apply --applier-mode will still try to apply the series even when the project doesn't have git.{push_to,public_repo,url_template} properties, then save the result and log. Technically, as long as the Project.git field is correct, git am can be attempted.

This is the case on current next.patchew.org, and in general makes testing applier code easier. Although I agree this shouldn't exist in a real configuration.

famz commented 6 years ago

BTW I took down next.patchew.org last week due to a server error. Will re-deploy with current master as the Ansible patches are merged, after the Chinese New Year.

bonzini commented 6 years ago

Oh, that makes sense then!

famz commented 6 years ago

Made the changes, but I propose we move to a mailing list + patchew.org workflow:

https://www.freelists.org/post/patchew-devel/PATCH-v3-02-Add-subproject-support

https://patchew.org/Patchew/20180222143731.21595-1-famz@redhat.com/