All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC updates for 3.4
Date: Thu, 26 Jan 2012 16:43:23 +0100	[thread overview]
Message-ID: <s5hmx9av59g.wl%tiwai@suse.de> (raw)
In-Reply-To: <20120125113508.GC3687@opensource.wolfsonmicro.com>

At Wed, 25 Jan 2012 11:35:09 +0000,
Mark Brown wrote:
> 
> [1  <text/plain; us-ascii (quoted-printable)>]
> 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

  reply	other threads:[~2012-01-26 15:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-24 20:11 ASoC updates for 3.4 Mark Brown
2012-01-24 20:33 ` Takashi Iwai
2012-01-24 20:46   ` Mark Brown
2012-01-25  9:14     ` Takashi Iwai
2012-01-25 11:35       ` Mark Brown
2012-01-26 15:43         ` Takashi Iwai [this message]
2012-01-26 15:57           ` Mark Brown
2012-01-26 16:10             ` Takashi Iwai
2012-01-26 16:40               ` Mark Brown
2012-01-26 16:46                 ` Takashi Iwai
     [not found] <20120304153255.GB4978@opensource.wolfsonmicro.com>
2012-03-05 12:21 ` Mark Brown
2012-03-05 14:17   ` Takashi Iwai
2012-03-06 13:02 Mark Brown
2012-03-06 13:47 ` Takashi Iwai
2012-03-14 14:07 Mark Brown
2012-03-15  6:39 ` Takashi Iwai
2012-03-29 12:08 Mark Brown
2012-03-29 16:02 ` Takashi Iwai
2012-03-29 16:35   ` Mark Brown
2012-04-07 10:21 Mark Brown
2012-04-07 10:31 ` Takashi Iwai
2012-04-23 16:28 Mark Brown
2012-04-23 16:41 ` Takashi Iwai
2012-05-02  9:30 Mark Brown
2012-05-05  9:38 ` 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=s5hmx9av59g.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    /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.