On 08.02.2023 21:58, Demi Marie Obenour wrote:
> Obtaining code over an insecure transport is a terrible idea for
> blatently obvious reasons.  Even for non-executable data, insecure
> transports are considered deprecated.
> 
> Demi Marie Obenour (4):
>   Build system: Replace git:// and http:// with https://
>   Automation and CI: Replace git:// and http:// with https://
>   Miscellaneous and documentation: Only use TLS-protected transports
>   GPL License Boilerplate: Switch from HTTP to HTTPS

Mind me asking what changed from v1? Neither here nor in the individual
patches there's any information about that. Yet especially for the
voluminous patches it would be quite relevant, to avoid reviewers needing
to go through everything again that they may have checked already.

Furthermore I'd like to ask that in submissions of new versions you drop
recipients whose email addresses bounce. Like I did get bounces from
Quan Xu's, I'd expect you did as well.

Thanks, Jan

Reply via email to