From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: RFC: Using '--no-output-indicator-old' to only show new state
Date: Fri, 11 Mar 2022 14:42:32 -0500 [thread overview]
Message-ID: <20220311194232.huwvcsar5iglswne@meerkat.local> (raw)
In-Reply-To: <CAHk-=wgT9=3V60koHO40omnubeBK3bD8kX8WAx+gUHTWoNCn4Q@mail.gmail.com>
On Fri, Mar 11, 2022 at 11:15:10AM -0800, Linus Torvalds wrote:
> So, for example, I could trivially use "torvalds@kernel.org" to send
> out patches, but I've tried to avoid having multiple active email
> accounts and confusing people with different names etc.
FWIW, you can send mail through mail.kernel.org with your regular
torvalds@linux-foundation.org email. This is what akpm does, and it's kosher
as far as DKIM/DMARC is concerned.
If you'd like to try that out, you can set that up with git-send-email:
https://korg.docs.kernel.org/mail.html#sending-outgoing-mail
Just set your sendemail.from=torvalds@linux-foundation.org instead of
torvalds@kernel.org.
-K
prev parent reply other threads:[~2022-03-11 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 19:40 RFC: Using '--no-output-indicator-old' to only show new state Linus Torvalds
2022-03-10 20:13 ` Junio C Hamano
2022-03-10 20:40 ` Linus Torvalds
2022-03-10 21:26 ` Junio C Hamano
2022-03-10 22:13 ` Linus Torvalds
2022-03-11 0:01 ` Linus Torvalds
2022-03-11 7:48 ` Ævar Arnfjörð Bjarmason
2022-03-11 9:45 ` [PATCH] parse-options: add per-option flag to stop abbreviation Ævar Arnfjörð Bjarmason
2022-03-11 18:44 ` Linus Torvalds
2022-03-11 19:15 ` RFC: Using '--no-output-indicator-old' to only show new state Linus Torvalds
2022-03-11 19:42 ` Konstantin Ryabitsev [this message]
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=20220311194232.huwvcsar5iglswne@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).