All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: ALSA development <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: The new alsa-driver repository
Date: Mon, 17 Dec 2012 16:52:28 +0100	[thread overview]
Message-ID: <50CF3FBC.7010309@perex.cz> (raw)

Hello all,

	the ALSA server has new alsa-driver repository which contains several
branches for now:

master	- just empty one with README
build   - the previous master branch
	  (but all was moved to the alsa/ subtree)
mirror	- mirrored code from upstream (ALSA parts only)
release	- merging branch for mirror/build trees to create
	  a relationship between them

All branches are ophan. It means that they have no common parent.

I put some handy configuration hints to the ALSA WIKI:

http://www.alsa-project.org/main/index.php/GIT_Server#Syncing_the_branch_release_in_alsa-driver.git

The reason to move the old master branch to the alsa/ subtree is quite
simple - you can merge/pull the branch to the full linux-2.6 kernel tree
now and do your development there. Also, cherry picks between mirror and
the linux-2.6 tree should work.

Another handy extension - in the current repo - might be to create the
linux-2.6 branch with the whole upstream and create another branch for
merging the build branch with the whole tree like 'release26' or so. In
this way, we can manage another releases of the out-of-kernel build code
for the ALSA tree in stable linux kernel versions.

Comments, other ideas are welcome.

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.

             reply	other threads:[~2012-12-17 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 15:52 Jaroslav Kysela [this message]
2012-12-17 16:12 ` The new alsa-driver repository Takashi Iwai

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=50CF3FBC.7010309@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.