[PATCH] gitpublish: Drop custom prefix
Now that all projects except the main library are using GitLab merge requests, all the patches that end up on libvir-list are by definition intended for libvirt itself rather than one of the subprojects, and so it's no longer necessary to include additional information in the mail subject. Signed-off-by: Andrea Bolognani <abologna@redhat.com> --- .gitpublish | 1 - 1 file changed, 1 deletion(-) diff --git a/.gitpublish b/.gitpublish index d37bf4174a..857f0d552c 100644 --- a/.gitpublish +++ b/.gitpublish @@ -1,4 +1,3 @@ [gitpublishprofile "default"] base = master to = libvir-list@redhat.com -prefix = libvirt PATCH -- 2.26.2
On Wed, Mar 03, 2021 at 11:11:51AM +0100, Andrea Bolognani wrote:
Now that all projects except the main library are using GitLab merge requests, all the patches that end up on libvir-list are by definition intended for libvirt itself rather than one of the subprojects, and so it's no longer necessary to include additional information in the mail subject.
It is still useful to have libvirt in the subject as a person's inbox may have mail from multiple different mailing lists, and this subject prefix distinguishes them. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
On Wed, 2021-03-03 at 10:22 +0000, Daniel P. Berrangé wrote:
On Wed, Mar 03, 2021 at 11:11:51AM +0100, Andrea Bolognani wrote:
Now that all projects except the main library are using GitLab merge requests, all the patches that end up on libvir-list are by definition intended for libvirt itself rather than one of the subprojects, and so it's no longer necessary to include additional information in the mail subject.
It is still useful to have libvirt in the subject as a person's inbox may have mail from multiple different mailing lists, and this subject prefix distinguishes them.
That will not work reliably as it's not enforced. Looking at the virtualization-related mailing lists I'm subscribed to, on qemu-devel the prefix is never used, and on both libvir-list and virt-tools-list you can find patches using it as well as patches not using it. -- Andrea Bolognani / Red Hat / Virtualization
On Wed, Mar 03, 2021 at 11:50:37AM +0100, Andrea Bolognani wrote:
On Wed, 2021-03-03 at 10:22 +0000, Daniel P. Berrangé wrote:
On Wed, Mar 03, 2021 at 11:11:51AM +0100, Andrea Bolognani wrote:
Now that all projects except the main library are using GitLab merge requests, all the patches that end up on libvir-list are by definition intended for libvirt itself rather than one of the subprojects, and so it's no longer necessary to include additional information in the mail subject.
It is still useful to have libvirt in the subject as a person's inbox may have mail from multiple different mailing lists, and this subject prefix distinguishes them.
That will not work reliably as it's not enforced.
This has been true forever, but it is none the less useful. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
participants (2)
-
Andrea Bolognani -
Daniel P. Berrangé