On Mon, Jul 23, 2018 at 12:06 PM Laura Abbott
> On 07/22/2018 12:12 PM, stan wrote:
>> On Sun, 22 Jul 2018 18:49:36 +0100
>> Sérgio Basto <sergio(a)serjux.com> wrote:
>>> Hello , I need bisect kernel between kernel 4.15-git1 and 4.15.0-git2
>>> where I find a git tree with these commits (patch-4.14-git1.xz to
>>> patch-4.14-git2.xz) ?
>>> this request is related with my nvidia that starts to fail since
>>> kernels 4.15.0 
>> I think this is the definitive git repository for the linux kernel.
>> Can't advise you on how to find what you are looking for, though.
> That's going to be a mirror, the official official repository is
> To your actual question, if you look at the commits in
> the fedora src git where those files were added, you'll see
> a commit hash in the commit message, so in this case it's
> 1a5d24760948 ("Linux v4.14-104-g1e19bded7f5d") and
> 2ef4e8028f50 ("Linux v4.14-2229-g894025f24bd0") . The
> part after the g is the hash in the kernel.org
> $ git log --oneline 1e19bded7f5d..894025f24bd0 | wc -l
> It's kind of a pain to figure out. I'd welcome suggestions
> about how to make this easier.
Could use the exploded tree and just do: git checkout kernel-<NVR>, as
each build has a corresponding tag.
although that still leaves the question of figuring out the base
to pass to git bisect. Maybe git is smart enough to do the right
thing with the patches on top?