[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130801095708.b43c432b2bf914827fd45d79@canb.auug.org.au>
Date: Thu, 1 Aug 2013 09:57:08 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Valdis Kletnieks <Valdis.Kletnieks@...edu>
Cc: linux-kernel@...r.kernel.org
Subject: Re: Stupid linux-next git question...
Hi Valdis,
On Wed, 31 Jul 2013 18:58:13 -0400 Valdis Kletnieks <Valdis.Kletnieks@...edu> wrote:
>
> OK... So I have (as usual) found some issues in linux-next, so I'm looking at 3
> bisects. I already know that bisecting between (say) next-20130715 and
> next-20130730 won't work, but bisecting between the 3.11-rc1 base of
> next-20130715 and next-20130730 *will* work.
>
> Question 1:
>
> Does bisecting between "the HEAD of Linus's tree when a given next- is built"
> and "some later next-" work? (basically, I know that anything in Linus's tree
> as of -0715 is 'Good', so I'd rather start from there than from 3.11-rc1 to
> save several bisects).
Yes, because that point only moves forward (obviously).
> Question 2:
>
> If that works, how do I determine the commit ID to feed to 'git bisect good'?
> I *hope* this in Next/merge.log is the magic I'm looking for:
>
> $ git reset --hard stable
> HEAD is now at 6c504ec Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux
> Merging origin/master (5ae90d8 Linux 3.11-rc3)
Yes, that, or if you look in Next/SHA1s, my start point in Linus' tree is
labelled "origin". Also, it is the "stable" branch in the current
linux-next tree (which is moved forward each day).
These are not stupid questions, by the way :-)
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists