[alsa-devel] HG vs GIT

Trent Piepho xyzzy at speakeasy.org
Thu Feb 7 16:49:39 CET 2008

On Thu, 7 Feb 2008, Takashi Iwai wrote:
> At Thu, 7 Feb 2008 14:52:43 +0100 (CET),
> > > > How do I test the driver if it's compiled with the kernel in the alsa.git
> > > > tree?  I want to compile the driver against the kernel I'm running now.
> > >
> > > Well, I don't get your point.  "git-pull alsa.git" onto your current
> > > kernel tree and make.  Then you have the latest ALSA drivers for your
> > > current system...
> >
> > Pull cannot be used. You'll pull also Linus's changes in tree with this
> > command (which might not be wanted).
> Ah, OK, I didn't think that your current tree is behind the ALSA
> tree.  But surely there must be an easy way to do that.  At easiest,
> I'd make a diff of alsa-git.tree to the upstream and apply it over the
> local tree.

It would have to be behind the current tree, unless you reboot multiple
times per day.

The problem with an out of tree codebase extracted from git (or Hg), is
that once extracted you couldn't use ALSA's SCM on it.  E.g., generating
nice patches based on current head, or pulling and merging recent patches
in with your current work.

I have a dozen different v4l-dvb Hg branches aka repositories on my system,
for different features or projects, etc.  What branches are for.  Some are
months old.  I can work on any one of those branches, compile, load, and
test the drivers, and push new changes to that branch, without rebooting.
I can do the same with ALSA too in fact, though the ALSA out of tree build
system is less convenient.  I'm not going to reboot five times a day.  I
only have one computer, and I'm not going to chance my recoding of the new
episode of Lost tonight getting messed up because of a problem in a one day
old kernel that hasn't been tested.

I don't have to reboot between 2.6.21 or 2.6.25-rc1 to work on a different

More information about the Alsa-devel mailing list