All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa cvs not building on top of 2.6.10-rc2-mm3-V0.7.32_14
Date: Fri, 10 Dec 2004 01:39:35 -0500	[thread overview]
Message-ID: <1102660775.29000.4.camel@krustophenia.net> (raw)
In-Reply-To: <1102659979.24675.6.camel@krustophenia.net>

On Fri, 2004-12-10 at 01:26 -0500, Lee Revell wrote:
> On Thu, 2004-12-09 at 21:38 -0800, Fernando Lopez-Lezcano wrote:
> > I can't seem to build current alsa cvs on top of
> > 2.6.10-rc2-mm3-V0.7.32-14...
> 
> I think I had this problem, and it went away mysteriously.  I can't
> reproduce it now.  Try a clean cvs checkout.

This was bug 605.

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=605

But the bug was closed.

I had a problem recently where "cvs update" did not seem to update my
tree to the latest version, I had to delete it and checkout again.  I
chalked this up to user error but maybe there's something weird going
on.

Lee



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

  reply	other threads:[~2004-12-10  6:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  5:38 alsa cvs not building on top of 2.6.10-rc2-mm3-V0.7.32_14 Fernando Lopez-Lezcano
2004-12-10  6:26 ` Lee Revell
2004-12-10  6:39   ` Lee Revell [this message]
2004-12-10 18:48   ` Fernando Lopez-Lezcano
2004-12-10 18:55     ` Takashi Iwai
2004-12-10 20:08       ` Fernando Lopez-Lezcano
2004-12-10 20:37         ` Fernando Lopez-Lezcano
2004-12-11 15:28         ` 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=1102660775.29000.4.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=nando@ccrma.Stanford.EDU \
    /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.