git.vger.kernel.org archive mirror
 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>,
	git@vger.kernel.org
Subject: Re: ASoC updates for v3.8
Date: Mon, 17 Dec 2012 15:45:59 +0100	[thread overview]
Message-ID: <s5hsj74wxco.wl%tiwai@suse.de> (raw)
In-Reply-To: <20121217142500.GG4985@opensource.wolfsonmicro.com>

At Mon, 17 Dec 2012 14:25:00 +0000,
Mark Brown wrote:
> 
> On Mon, Dec 17, 2012 at 03:09:34PM +0100, Takashi Iwai wrote:
> > At Mon, 17 Dec 2012 22:14:10 +0900,
> > Mark Brown wrote:
> > > 
> > > The following changes since commit 29594404d7fe73cd80eaa4ee8c43dcc53970c60e:
> > > 
> > >   Linux 3.7 (2012-12-10 19:30:57 -0800)
> > > 
> > > are available in the git repository at:
> > > 
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
> 
> > No signed tag?
> 
> Oh, ffs.  There's a tag asoc-3.8p1 which should have been there for days
> but git's doing it's usual thing and silently substituting in a branch
> for a tag.  This is monumentally unhelpful, especially since it doesn't
> even print a warning but rather just silently substitutes.
 
Yeah, this too kind feature bites me often.

> You can tell there's a signed tag from the way the message from the tag
> is included in the pull request.

Yes, I expected that, but not I wasn't sure which tag to take.
I thought you use tags/asoc-3.8, and I tried it, but this time it
isn't.

In anyway, pulled now.  Thanks.


Takashi

      reply	other threads:[~2012-12-17 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121217131410.GB4985@opensource.wolfsonmicro.com>
     [not found] ` <s5hy5gwwz1d.wl%tiwai@suse.de>
2012-12-17 14:25   ` ASoC updates for v3.8 Mark Brown
2012-12-17 14:45     ` Takashi Iwai [this message]

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=s5hsj74wxco.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=git@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).