[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Nov 2009 22:34:22 +0100
From: Frans Pop <elendil@...net.nl>
To: Stephen Hemminger <shemminger@...tta.com>
Cc: jens.axboe@...cle.com, linux-kernel@...r.kernel.org
Subject: Re: Mount -o sync regression in 2.6.31
Stephen Hemminger wrote:
> I tried the obvious bisection, but git bisect seems to wonder off into
> the weeds now. There is no reason that bisecting between v2.6.30 and
> v2.6.31-rc1 should go off into v2.6.30-rc2
AFAIK that can happen if some branch was merged after 2.6.30 that happened
to be based on a commit from v2.6.30-rc2. Did you check in what branch you
were when that happened?
If you look at 'gitk v2.6.30..v2.6.31-rc1' and scroll to the bottom, you
will see quite a few merges of branches that were based on commits from
(early) v2.6.30-rcX releases.
Cheers.
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists