From: Takashi Iwai Subject: Re: ASoC updates for 3.4 Date: Thu, 26 Jan 2012 16:43:23 +0100 Message-ID: References: <20120124201157.GB1135@opensource.wolfsonmicro.com> <20120124204615.GE1135@opensource.wolfsonmicro.com> <20120125113508.GC3687@opensource.wolfsonmicro.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id 64B2A24376 for ; Thu, 26 Jan 2012 16:43:26 +0100 (CET) In-Reply-To: <20120125113508.GC3687@opensource.wolfsonmicro.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Mark Brown Cc: alsa-devel@alsa-project.org, Liam Girdwood List-Id: alsa-devel@alsa-project.org At Wed, 25 Jan 2012 11:35:09 +0000, Mark Brown wrote: > > [1 ] > On Wed, Jan 25, 2012 at 10:14:42AM +0100, Takashi Iwai wrote: > > Mark Brown wrote: > > > On Tue, Jan 24, 2012 at 09:33:47PM +0100, Takashi Iwai wrote: > > > > > Yeah, my git is still 1.7.8.x and it doesn't seem to work well with > > > > Oh, well. I think it's the tag rather than the signed bit. > > > I'm not entirely sure who to blame. The error message is: > > > > % git pull git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git asoc-3.3-20120124 > > fatal: Couldn't find remote ref asoc-3.3-20120124 > > That's the tagging - older (and by older I mean "currently released") > versions of git can only pull from branches so that's just saying it > can't find the tag object. It seems that the problem is rather in the server side. I updated the git to version 1.7.9.rc2, but it still gives the same error at pull. Meanwhile, I could pull a signed tag from a local tree. Or I'm overlooking something obvious. BTW, the pull of a signed tag gives always a merge commit even if it can be fast-forwarded. The --ff option doesn't work, too. This is the intended behavior, AFAIK. OTOH, we don't want to see too many merge commits in a straight development line while the development phase. So, pulling signed tags from you while development might be not always ideal, if we want to keep the sound git trees better in sync. thanks, Takashi