All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs <linux-xfs@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] maintainers: update my email address
Date: Sat, 9 Jan 2021 11:00:01 -0800	[thread overview]
Message-ID: <CAHk-=wibYWuriC4m-zjU10J65peMDAFTjY2EGjTV=COgg1saPw@mail.gmail.com> (raw)
In-Reply-To: <20210109064602.GU6918@magnolia>

On Fri, Jan 8, 2021 at 10:46 PM Darrick J. Wong <darrick.wong@oracle.com> wrote:
>
> Change my email contact ahead of a likely painful eleven-month migration
> to a certain cobalt enteprisey groupware cloud product that will totally
> break my workflow.  Some day I may get used to having to email being
> sequestered behind both claret and cerulean oath2+sms 2fa layers, but
> for now I'll stick with keying in one password to receive an email vs.
> the required four.

So I appreciate this email coming from your old email address, but I
also just want to note that as long as you then use the oracle email
address for sending email, commit authorship, and "Signed-off-by:" (or
Acked-by etc) addresses, those tend to be the ones that _primarily_
get used when people then CC you on issues.

Well, at least that's how I work. The MAINTAINERS file tends to be the
secondary one.

But I wish you best of luck with the new email setup ;)

            Linus

  reply	other threads:[~2021-01-09 19:01 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09  6:46 [PATCH] maintainers: update my email address Darrick J. Wong
2021-01-09 19:00 ` Linus Torvalds [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-12 12:37 [PATCH] MAINTAINERS: Update " Bin Meng
2024-04-12 17:33 ` Philippe Mathieu-Daudé
2024-02-01  2:10 Leo Yan
2023-10-08 10:58 [PATCH] MAINTAINERS: update " Ondřej Jirman
2023-10-08 10:58 ` Ondřej Jirman
2023-08-03 13:40 David Rheinsberg
2023-08-14  9:55 ` Jiri Kosina
2022-01-14 17:07 Nick Rosbrook
2022-01-17 10:09 ` George Dunlap
2022-01-17 10:21 ` Bertrand Marquis
2021-09-20  7:28 Bartosz Golaszewski
2021-09-20  9:42 ` Andy Shevchenko
2021-09-20 11:41   ` Bartosz Golaszewski
2021-09-23 21:50 ` Linus Walleij
2021-09-29 21:01 ` Wolfram Sang
2021-09-30  7:17   ` Bartosz Golaszewski
2020-10-27  6:02 Michael Roth
2020-10-28 20:56 ` Thomas Huth
2020-12-13 15:58   ` Laurent Vivier
2020-12-13 16:04     ` Laurent Vivier
2020-10-05 16:45 Antoine Tenart
2020-08-26 14:47 [PATCH] MAINTAINERS: Update " Ian Jackson
2020-03-11 20:05 Stephen Smalley
2020-03-12 15:01 ` Paul Moore
2020-01-22 10:18 Andrew Murray
2020-01-22 10:53 ` Lorenzo Pieralisi
2019-12-09  9:39 [PATCH] MAINTAINERS: update " lukasz.luba
2019-12-09 17:53 ` Krzysztof Kozlowski
2019-12-10  9:46   ` Lukasz Luba
2019-07-22 13:44 [PATCH] MAINTAINERS: Update " Jean-Philippe Brucker
2019-07-22 13:44 Jean-Philippe Brucker
2019-07-22 13:44 ` Jean-Philippe Brucker
2019-07-22 13:44 ` Jean-Philippe Brucker
2019-07-22 13:44 ` Jean-Philippe Brucker
2019-07-22 13:56 ` Will Deacon
2019-07-22 13:56 ` Will Deacon
2019-07-22 13:56   ` Will Deacon
2019-07-22 13:56   ` Will Deacon
2019-07-22 13:56   ` Will Deacon
2019-07-18 19:24 Maxime Ripard
2019-07-18 19:24 ` Maxime Ripard
2019-07-18 19:24 ` Maxime Ripard
2019-07-23  9:26 ` Maxime Ripard
2019-07-23  9:26   ` Maxime Ripard
2019-07-23  9:26   ` Maxime Ripard
2019-07-17 10:32 Julien Thierry
2019-07-17 10:32 ` Julien Thierry
2019-07-17 10:32 ` Julien Thierry
2019-07-17 11:36 ` Marc Zyngier
2019-07-17 11:36   ` Marc Zyngier
2019-07-17 11:36   ` Marc Zyngier
2019-07-17 11:43 ` Will Deacon
2019-07-17 11:43   ` Will Deacon
2019-07-17 11:43   ` Will Deacon
2019-06-15  8:21 Hanjun Guo
2019-06-15  8:21 ` Hanjun Guo
2019-06-17  7:56 ` Marc Zyngier
2019-06-17  7:56   ` Marc Zyngier
2019-06-17  8:44   ` Hanjun Guo
2019-06-17  8:44     ` Hanjun Guo
2019-05-24 15:24 [PATCH] MAINTAINERS: update " Wei Liu
2019-05-24 15:51 ` Jan Beulich
2019-05-24 15:52 ` George Dunlap
2018-12-03 10:23 [PATCH] MAINTAINERS: Update " Boris Brezillon
2018-04-04 12:03 [PATCH] MAINTAINERS: update " Bernat, Yehezkel
2018-04-05 10:28 ` Mika Westerberg
2018-01-03  4:14 [PATCH] MAINTAINERS: Update " Pravin B Shelar
2018-01-03 15:20 ` Joe Perches
2018-01-04 18:38 ` David Miller
2018-01-05  3:28   ` Pravin Shelar
2017-10-05 20:39 Michal Marek
2017-10-12 13:43 ` Jiri Kosina
2017-02-03 11:18 [PATCH] MAINTAINERS: update " Amit Shah
2017-02-03 11:18 ` Amit Shah
2017-02-03 15:11 ` Michael S. Tsirkin
2017-02-03 15:11   ` Michael S. Tsirkin
2017-02-03 15:34   ` Amit Shah
2017-02-03 15:34     ` Amit Shah
2016-04-24 13:54 Chao Yu
2015-03-11 20:18 [PATCH] MAINTAINERS: Update " chas williams - CONTRACTOR
2015-03-11 20:49 ` David Miller
2012-03-06  0:58 [PATCH] MAINTAINERS: update " Stephen Warren
2012-03-06  0:58 ` Stephen Warren
2012-03-06  0:58 ` Stephen Warren
     [not found] ` <1330995516-22160-1-git-send-email-swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-03-07 22:56   ` Olof Johansson
2012-03-07 22:56     ` Olof Johansson
2012-03-07 22:56     ` Olof Johansson

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='CAHk-=wibYWuriC4m-zjU10J65peMDAFTjY2EGjTV=COgg1saPw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=darrick.wong@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.