[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72k5+0RLJU6_agbFK6c61ogRt6ASGuXfRWAKYJPwqtB8BA@mail.gmail.com>
Date: Wed, 7 Jul 2021 00:14:14 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Pedro Tammela <pctammela@...il.com>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
rust-for-linux <rust-for-linux@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Doc Mailing List <linux-doc@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...gle.com>
Subject: Re: [PATCH 16/17] MAINTAINERS: Rust
On Tue, Jul 6, 2021 at 2:26 AM Pedro Tammela <pctammela@...il.com> wrote:
>
> Does this mean that development will be done exclusively on GitHub?
> If affirmative, is there a bot that will replicate the messages in the
> mailing list?
Development has happened mainly in GitHub so far, but we have accepted
patches from the ML and we can do their reviews there too.
We do not have a bot to replicate reviews into the mailing list nor
any fancy bidirectional sync, though.
If this is deemed unacceptable by Linus et. al., we can do development
in the ML as usual -- we do not really mind one way or the other (and,
in fact, we discussed moving things to a git.kernel.org tree too).
The main point of GitHub/GitLab/etc. for us so far is having an issue
tracker and some kind of CI.
Cheers,
Miguel
Powered by blists - more mailing lists