From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
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 16:15:20 +0100 [thread overview]
Message-ID: <CAHmME9q_hYyiUKb+H82-njugXaruQc6=sVa3HCQHnOHEOsGVwQ@mail.gmail.com> (raw)
In-Reply-To: <YauCkjsgDL4sdCId@mit.edu>
Hi Ted,
On Sat, Dec 4, 2021 at 4:00 PM Theodore Y. Ts'o <tytso@mit.edu> wrote:
> 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?
Sure, that works for me. I had started using zx2c4/random.git. But
I'll talk to Konstantin about moving that over to a shared repository
in a group namespace.
Jason
next prev parent reply other threads:[~2021-12-04 15:15 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
2021-12-04 15:15 ` Jason A. Donenfeld [this message]
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='CAHmME9q_hYyiUKb+H82-njugXaruQc6=sVa3HCQHnOHEOsGVwQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).