All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Joe Perches <joe@perches.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: co-maintain random.c
Date: Sat, 4 Dec 2021 10:00:34 -0500	[thread overview]
Message-ID: <YauCkjsgDL4sdCId@mit.edu> (raw)
In-Reply-To: <CAHmME9q7kVREOGPpG+kafS25Ny1=geFPwLRREe+nkC=UkGQUHw@mail.gmail.com>

On Wed, Dec 01, 2021 at 11:05:31AM -0500, Jason A. Donenfeld wrote:
> Hi Joe,
> 
> On Tue, Nov 30, 2021 at 8:01 PM Joe Perches <joe@perches.com> wrote:
> > I suggest you reverse the entry order too as Ted really
> > hasn't done much to random.c for quite awhile.
> 
> Linus applied this already, but also, I both don't think the order
> really matters that much, and I'd really rather this be a "co-" thing,
> rather than rocking the boat.

Jason,

Thanks for stepping up.  There's no question that this Fall has been
insanely busy for me, and for the past 3 weeks or so, I've been on
vacation and Thanksgiving travel, and I'm still catching up on a
mountain of e-mail.

Something that I think would make sense is that we set up a joint git
tree on git.kernel.org, for which we would both have access to push
to, and use a group maintainership model much like what other teams
have done.  Do you agree?

						- Ted

  reply	other threads:[~2021-12-04 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 18:43 [PATCH] MAINTAINERS: co-maintain random.c Jason A. Donenfeld
2021-12-01  1:01 ` Joe Perches
2021-12-01 16:05   ` Jason A. Donenfeld
2021-12-04 15:00     ` Theodore Y. Ts'o [this message]
2021-12-04 15:15       ` Jason A. Donenfeld
2021-12-07 15:49         ` Jason A. Donenfeld
2021-12-07 18:01           ` Theodore Y. Ts'o
2021-12-01 20:56   ` Joe Perches

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=YauCkjsgDL4sdCId@mit.edu \
    --to=tytso@mit.edu \
    --cc=Jason@zx2c4.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@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 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.