At Tue, 29 Jan 2008 19:19:48 +0100, Martin Egge wrote: > > Hi, > > Am Dienstag, 29. Januar 2008 schrieb Takashi Iwai: > > Thanks. It's weird that there is really no significant difference in > > these proc files. So it should be something else. > > > > Could you try HG bisect? It'd be greatly helpful. > > What does HG bisect mean? Run "hg bisect -h". It's a method to track down the regression point during changesets. A brief instruction is below: - First, initizliaze % hg bisect init - Go to the broken point (usually the latest changeset, tip) % hg update -rtip - Mark it as bad % hg bisect bad - Go to the changeset that is known to work (e.g. v1.0.15) % hg update -rv1.0.15 - Mark it as good % hg bisect good then the bisect will move to a next changeset to try. - Try this changeset, and mark either good or bad. - Repeat until the problematic changeset is found. - Reset bisect % hg bisect reset Note that when you need an additonal patch, you have to apply the patch at each time, and revert it (hg revert --all) before marking good/bad. Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
