From: Rene Herman <rene.herman@keyaccess.nl>
To: Takashi Iwai <tiwai@suse.de>, ALSA devel <alsa-devel@alsa-project.org>
Subject: GIT: something wrong with sound-2.6/devel?
Date: Sun, 20 Jul 2008 20:56:20 +0200 [thread overview]
Message-ID: <48838A54.40404@keyaccess.nl> (raw)
Hi Takashi.
Is there something wrong with your devel branch or is it me?
rene@7ixe4:~/src/linux/7ixe4$ git fetch tiwai
remote: Counting objects: 1695, done.
remote: Compressing objects: 100% (418/418), done.
remote: Total 1418 (delta 1182), reused 1222 (delta 1000)
Receiving objects: 100% (1418/1418), 275.35 KiB, done.
Resolving deltas: 100% (1182/1182), completed with 170 local objects.
From git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6
! [rejected] devel -> tiwai/devel (non fast forward)
! [rejected] dma-fix -> tiwai/dma-fix (non fast forward)
3e14b50..9432484 for-linus -> tiwai/for-linus
! [rejected] master -> tiwai/master (non fast forward)
481c534..50515af upstream -> tiwai/upstream
rene@7ixe4:~/src/linux/7ixe4$ git checkout -b head v2.6.26
Switched to a new branch "head"
rene@7ixe4:~/src/linux/7ixe4$ git merge tiwai/devel
Auto-merged sound/pci/ac97/ac97_patch.c
Auto-merged sound/pci/emu10k1/emu10k1_main.c
Auto-merged sound/pci/hda/patch_analog.c
Auto-merged sound/pci/hda/patch_realtek.c
CONFLICT (content): Merge conflict in sound/pci/hda/patch_realtek.c
Auto-merged sound/pci/hda/patch_sigmatel.c
Automatic merge failed; fix conflicts and then commit the result.
It's no doubt trivial to fixup, but I believe this should've merged
cleanly? (the master branch from where I'm branching off head is an
undisturbed linus tree).
Rene.
next reply other threads:[~2008-07-20 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-20 18:56 Rene Herman [this message]
2008-07-20 19:08 ` GIT: something wrong with sound-2.6/devel? Jaroslav Kysela
2008-07-20 19:35 ` Rene Herman
2008-07-20 20:04 ` Rene Herman
2008-07-21 8:45 ` Rene Herman
2008-07-21 9:51 ` Mark Brown
2008-07-21 10:39 ` Rene Herman
2008-07-21 10:47 ` Mark Brown
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=48838A54.40404@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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.