Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Zwisler <zwisler@google.com>
To: alsa-devel@alsa-project.org,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Mark Brown <broonie@kernel.org>
Subject: Correct git tree for ALSA development
Date: Mon, 29 Apr 2019 14:29:18 -0600	[thread overview]
Message-ID: <20190429202918.GA35915@google.com> (raw)

Hi,

I'm trying to ramp up a bit on ALSA development, and I noticed that many
sound-related entries in MAINTAINERS still refer to alsa-kernel.git hosted on
alsa-project.org, i.e.:

BT87X AUDIO DRIVER
M:      Clemens Ladisch <clemens@ladisch.de>
L:      alsa-devel@alsa-project.org (moderated for non-subscribers)
T:      git git://git.alsa-project.org/alsa-kernel.git
S:      Maintained
F:      Documentation/sound/cards/bt87x.rst
F:      sound/pci/bt87x.c

>From the alsa-project.org pages:

https://alsa-project.org/wiki/Download#Developers:_GIT_access
https://alsa-project.org/wiki/GIT_Server#For_developers_-_kernel_drivers

it seems like current development/maintenance actually happens somewhere else,
possibly on Mark Brown's kernel.org tree?

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/

If so, should we update those stale MAINTAINERS entries?

Thanks,
- Ross

             reply	other threads:[~2019-04-29 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29 20:29 Ross Zwisler [this message]
2019-05-02  1:35 ` Correct git tree for ALSA development Mark Brown

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=20190429202918.GA35915@google.com \
    --to=zwisler@google.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.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