From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
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 14:25:00 +0000 [thread overview]
Message-ID: <20121217142500.GG4985@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5hy5gwwz1d.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
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.
You can tell there's a signed tag from the way the message from the tag
is included in the pull request.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next parent reply other threads:[~2012-12-17 14:25 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 ` Mark Brown [this message]
2012-12-17 14:45 ` ASoC updates for v3.8 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=20121217142500.GG4985@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=git@vger.kernel.org \
--cc=lrg@ti.com \
--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 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).