From: Mark Brown <broonie@kernel.org>
To: Ross Zwisler <zwisler@google.com>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: Correct git tree for ALSA development
Date: Thu, 2 May 2019 10:35:56 +0900 [thread overview]
Message-ID: <20190502013556.GO14916@sirena.org.uk> (raw)
In-Reply-To: <20190429202918.GA35915@google.com>
[-- Attachment #1.1: Type: text/plain, Size: 536 bytes --]
On Mon, Apr 29, 2019 at 02:29:18PM -0600, Ross Zwisler wrote:
> it seems like current development/maintenance actually happens somewhere else,
> possibly on Mark Brown's kernel.org tree?
My tree and Takashi's tree for our work.
> If so, should we update those stale MAINTAINERS entries?
You need to check with the relevant submaintainers, they may well still
be using the relevant trees for their specific areas. If something is
listed separately in MAINTAINERS then there's a submaintainer who may be
maintaining their own stuff.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2019-05-02 1:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 20:29 Correct git tree for ALSA development Ross Zwisler
2019-05-02 1:35 ` Mark Brown [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=20190502013556.GO14916@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=zwisler@google.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 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.