All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Keith A. Milner" <maillist@superlative.org>
To: alsa-devel@alsa-project.org
Subject: CVS, git, or something else?
Date: Mon, 24 Nov 2008 23:10:29 +0000	[thread overview]
Message-ID: <200811242310.29792.maillist@superlative.org> (raw)

I've been trying to check out the latest alsa-driver source to do some work on 
it. I followed the instructions at:
http://www.alsa-project.org/main/index.php/GIT_Server#Occasional_Developers

But when I cd alsa-drivers and gitcompile, it fails:

make[1]: Entering directory 
`/homedirs/kamilner/Development/Workspace/alsa/alsa-driver/acore'
copying file alsa-kernel/core/init.c
patching file init.c
Hunk #2 succeeded at 280 (offset 3 lines).
Hunk #3 succeeded at 306 (offset 3 lines).
Hunk #4 FAILED at 568.
1 out of 4 hunks FAILED -- saving rejects to file init.c.rej
make[1]: *** [init.c] Error 1
make[1]: Leaving directory 
`/homedirs/kamilner/Development/Workspace/alsa/alsa-driver/acore'
make: *** [dep] Error 1

Do I have the right version? Am I going about this the right way? I see a lot 
of posts on this list talking about CVS but none mentioning git.

Maybe I should be using CVS instead?


-- 
Keith A. Milner

             reply	other threads:[~2008-11-24 23:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 23:10 Keith A. Milner [this message]
2008-11-24 23:47 ` CVS, git, or something else? Build patch failure Eliot Blennerhassett
2008-11-24 23:56   ` Keith A. Milner
2008-11-25  0:45     ` Eliot Blennerhassett
2008-11-25  0:49       ` Takashi Iwai
2008-11-25  1:00         ` Eliot Blennerhassett
2008-11-25  1:18           ` Takashi Iwai
2008-11-25 20:41             ` Eliot Blennerhassett
2008-11-25 23:53               ` Keith A. Milner
2008-11-26  0:44                 ` Keith A. Milner
2008-11-26  6:27               ` 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=200811242310.29792.maillist@superlative.org \
    --to=maillist@superlative.org \
    --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 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.