From: Jason Cooper <jason@lakedaemon.net>
To: Gene Heskett <gheskett@wdtv.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Git puzzle
Date: Sun, 29 Dec 2013 00:02:30 -0500 [thread overview]
Message-ID: <20131229050230.GL19878@titan.lakedaemon.net> (raw)
In-Reply-To: <20131229043547.GJ19878@titan.lakedaemon.net>
Gene,
On Sat, Dec 28, 2013 at 11:35:47PM -0500, Jason Cooper wrote:
> On Sat, Dec 28, 2013 at 09:41:40PM -0500, Gene Heskett wrote:
...
> > working toward 3.8.3 which doesn't, and I have the disk space chowned
> > to me, what is the exact syntax to pull a clone of 3.8.2, and then do
> > a bisect to 3.8.3 where the microcode update for an AMD phenom doesn't
> > work. Skipping fwd to 3.12.0 it still isn't working.
>
> The version tags you are referring to are from the linux-stable tree, so
> we'll clone that one instead of Linus'.
Just one small addendum to this:
Once you've identified the commit in the -stable tree, we'll have to
find the corresponding commit in the mainline tree. Don't worry about
trying to find this for your initial email, just make sure to mention
that the commit identified is from the -stable tree between v3.8.2 and
v3.8.3.
thx,
Jason.
next prev parent reply other threads:[~2013-12-29 5:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 2:41 Gene Heskett
2013-12-29 4:35 ` Jason Cooper
2013-12-29 5:02 ` Jason Cooper [this message]
2013-12-29 5:11 ` Gene Heskett
2013-12-29 5:25 ` Jason Cooper
2013-12-29 5:42 ` Gene Heskett
2013-12-29 6:02 ` Jason Cooper
2013-12-29 6:27 ` Gene Heskett
2013-12-29 6:47 ` Jason Cooper
2013-12-29 11:26 ` Gene Heskett
2013-12-29 9:30 ` Geert Uytterhoeven
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=20131229050230.GL19878@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=gheskett@wdtv.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®