From: David Sterba <dsterba@suse.cz>
To: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Cc: Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Nick Terrell <terrelln@fb.com>,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: btrfs: update development git tree location
Date: Mon, 14 Mar 2022 20:29:23 +0100 [thread overview]
Message-ID: <20220314192923.GP12643@twin.jikos.cz> (raw)
In-Reply-To: <20220314190907.23279-1-sweettea-kernel@dorminy.me>
On Mon, Mar 14, 2022 at 03:09:07PM -0400, Sweet Tea Dorminy wrote:
> Patches get pulled into a branch on github as listed, before eventually
> making it into a pull request using the kernel.org git repository.
> Development is expected to work off of the github branch, though, so
> list it in MAINTAINERS as a secondary tree.
We have this documented on the wiki
https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
I don't think it needs to be in the maintainers file.
prev parent reply other threads:[~2022-03-14 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:09 [PATCH] MAINTAINERS: btrfs: update development git tree location Sweet Tea Dorminy
2022-03-14 19:29 ` David Sterba [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=20220314192923.GP12643@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
--cc=terrelln@fb.com \
/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