Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eliot Blennerhassett <linux@audioscience.com>
To: alsa-devel@alsa-project.org
Subject: Re: HG -> GIT migration
Date: Wed, 21 May 2008 14:30:06 +1200	[thread overview]
Message-ID: <200805211430.06653.linux@audioscience.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0805201314190.1798@tm8103-a.perex-int.cz>

On Tuesday 20 May 2008 23:21:13 Jaroslav Kysela wrote:
> Hi all,
>
> 	I finished migration from HG to GIT. All repositories are
> converted and we have one "new" repository - alsa-kernel.git which is full
> Linux 2.6 GIT tree. The old HG alsa-kernel repository was renamed to
> alsa-kmirror 

Hi Jaroslav,

can you clarify what one should do to be able to build latest GIT head.

Should I expect the following to work? (as it used to work with Hg)

$ git clone git://git.alsa-project.org/alsa-kmirror.git alsa-kmirror  
$ git clone git://git.alsa-project.org/alsa-driver.git alsa-driver  
$ cd alsa-driver
$ ALSAKERNELDIR=../alsa-kmirror/ ./gitcompile --with-debug=full   

anyway I get this error

  CC [M]  /home/eliot/src/alsagit/alsa-driver/i2c/other/pt2258.o
make[4]: *** No rule to make target 
`/home/eliot/src/alsagit/alsa-driver/i2c/other/tea575x-tuner.o', needed by 
`/home/eliot/src/alsagit/alsa-driver/i2c/other/snd-ak4117.o'.  Stop.

regards

Eliot

  parent reply	other threads:[~2008-05-21  2:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 11:21 HG -> GIT migration Jaroslav Kysela
2008-05-20 14:12 ` Ben Stanley
2008-05-20 14:24   ` Jaroslav Kysela
2008-05-21  2:30 ` Eliot Blennerhassett [this message]
2008-05-21  6:09   ` Jaroslav Kysela
2008-05-21 10:28     ` Takashi Iwai
2008-05-21 12:30       ` Rene Herman
2008-05-21 12:37         ` Takashi Iwai
2008-05-21 13:04           ` Rene Herman
2008-05-21 13:48             ` [alsa-devel] " Jaroslav Kysela
2008-05-21 14:40               ` Rene Herman
2008-05-21 14:52                 ` Takashi Iwai
2008-05-21 15:29                   ` Rene Herman
2008-05-22  1:24                     ` [alsa-devel] " Stephen Rothwell
2008-05-22 20:43                       ` Rene Herman
2008-05-22 23:40                         ` Stephen Rothwell
2008-05-21 14:47             ` Takashi Iwai
2008-05-21 15:40               ` Rene Herman
2008-05-21 16:02                 ` Takashi Iwai
2008-05-21 16:16                   ` [alsa-devel] " Linus Torvalds
2008-05-21 16:51                     ` Takashi Iwai
2008-05-21 17:07                       ` Tobin Davis
2008-05-21 17:19                         ` Jaroslav Kysela
2008-05-21 17:22                         ` Rene Herman
2008-05-21 17:43                       ` [alsa-devel] " Linus Torvalds
2008-05-21 18:11                         ` Linus Torvalds
2008-05-21 18:25                           ` [alsa-devel] " david
2008-05-21 18:39                             ` Linus Torvalds
2008-05-21 18:49                             ` Takashi Iwai
2008-05-21 18:47                         ` Takashi Iwai
2008-05-21 19:02                           ` Linus Torvalds
2008-05-21 21:08                             ` Takashi Iwai
2008-05-22 14:23               ` [alsa-devel] " Dmitry Torokhov
2008-05-21 22:16     ` Eliot Blennerhassett
2008-05-23  2:31       ` Ben Stanley
2008-05-23  6:38         ` Jaroslav Kysela

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=200805211430.06653.linux@audioscience.com \
    --to=linux@audioscience.com \
    --cc=alsa-devel@alsa-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox