From: Joe Perches <joe@perches.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace HTTP links with HTTPS ones: documentation
Date: Mon, 25 May 2020 11:24:28 -0700 [thread overview]
Message-ID: <7b93effe211b5439b6b8697e8ed3a2b070bfbb31.camel@perches.com> (raw)
In-Reply-To: <0b3b5ae5-457a-b550-63a8-08a77bb862d7@al2klimov.de>
On Mon, 2020-05-25 at 20:01 +0200, Alexander A. Klimov wrote:
> Does it matter whether I just feed the output of ...
>
> perl scripts/get_maintainer.pl --separator , --norolestats
> 0001-Replace-HTTP-links-with-HTTPS-ones-documentation.patch
>
> ... into Git send-email To: prompt or actually CC: (not To:) mailing lists?
Yes. vger mailing lists drop emails with large to:/cc:
headers (It was >1024 chars, it may be different now)
It's generally better to add --nogit --nogit-fallback to
get_maintainer to avoid the git lookup addition of people
that have modified files that aren't listed in MAINTAINERS.
You could add a --bcc with those dropped names if you
really want to have those people receive the emails.
next prev parent reply other threads:[~2020-05-25 18:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 20:00 Alexander A. Klimov
[not found] ` <CAHZk5We1y7o+s7LG=7Q4mVynj5CvJ7RdXLx6WFd-k0yyk=DyPw@mail.gmail.com>
2020-05-22 9:18 ` Alexander A. Klimov
2020-05-25 16:28 ` Jonathan Corbet
2020-05-25 18:01 ` Alexander A. Klimov
2020-05-25 18:24 ` Joe Perches [this message]
2020-05-25 18:32 ` Alexander A. Klimov
2020-05-25 19:41 ` Jonathan Corbet
-- strict thread matches above, loose matches on Subject: below --
2020-05-26 6:05 Alexander A. Klimov
2020-06-08 15:33 ` Jonathan Corbet
2020-05-16 12:27 Alexander A. Klimov
2020-05-17 19:45 ` Jonathan Corbet
2020-05-17 20:00 ` Matthew Wilcox
2020-05-17 20:18 ` Alexander A. Klimov
2020-05-19 16:10 ` Jonathan Corbet
2020-05-19 18:50 ` Alexander A. Klimov
2020-05-19 19:43 ` Jonathan Corbet
2020-05-19 20:49 ` Andy Shevchenko
2020-05-19 22:04 ` Alexander A. Klimov
2020-05-20 8:25 ` Andy Shevchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b93effe211b5439b6b8697e8ed3a2b070bfbb31.camel@perches.com \
--to=joe@perches.com \
--cc=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome