From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86, microcode, AMD: Per-family patches cache
Date: Wed, 22 Aug 2012 16:26:25 -0700 [thread overview]
Message-ID: <50356AA1.1030503@zytor.com> (raw)
In-Reply-To: <503561A1.2040007@zytor.com>
On 08/22/2012 03:48 PM, H. Peter Anvin wrote:
>
> Weird. I have never had to git fetch --tags before...
>
OK, sorted. Next complaint... please don't mix urgent (for the current
version) and non-urgent (for next) in the same pull request.
I have sorted it out, but it made things take a lot longer on my part.
-hpa
next prev parent reply other threads:[~2012-08-22 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 14:30 [GIT PULL] x86, microcode, AMD: Per-family patches cache Borislav Petkov
2012-08-20 23:23 ` H. Peter Anvin
2012-08-21 9:16 ` Borislav Petkov
2012-08-22 22:48 ` H. Peter Anvin
2012-08-22 23:26 ` H. Peter Anvin [this message]
2012-08-23 9:51 ` Borislav Petkov
2012-08-22 21:52 ` H. Peter Anvin
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=50356AA1.1030503@zytor.com \
--to=hpa@zytor.com \
--cc=andreas.herrmann3@amd.com \
--cc=bp@amd64.org \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
/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.