From: Rene Herman <rene.herman@keyaccess.nl>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>, ALSA devel <alsa-devel@alsa-project.org>
Subject: GIT tree usage.
Date: Tue, 10 Jun 2008 23:19:12 +0200 [thread overview]
Message-ID: <484EEFD0.4070804@keyaccess.nl> (raw)
Good day.
I have been using Takashi's "sound-2.6" GIT repo:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
for pulling current ALSA (branch master) into the stock kernel tree and
while rebuilding stuff thought I'd try switching to the official ALSA
GIT repo(s). I'd like to make sure that I am now using the right trees
and branches...
I start out locally with a fresh linus clone:
$ git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 local
and then want to pull latest ALSA into it:
$ git remote add alsa git://git.alsa-project.org/alsa-kernel.git
$ git remote show alsa
* remote alsa
URL: git://git.alsa-project.org/alsa-kernel.git
Tracked remote branches
for-linus linux-2.6 master
$ git checkout -b current
$ git merge alsa/master
Am I using the right tree and branch for this? And is this branch being
rebased?
Rene.
next reply other threads:[~2008-06-10 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 21:19 Rene Herman [this message]
2008-06-10 21:25 ` GIT tree usage Rene Herman
2008-06-11 16:26 ` 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=484EEFD0.4070804@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
--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.