From: Frans Pop <elendil@planet.nl>
To: Stephen Hemminger <shemminger@vyatta.com>
Subject: Re: Mount -o sync regression in 2.6.31
Date: Wed, 11 Nov 2009 22:34:22 +0100
User-Agent: KMail/1.9.9
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org
References: <20091111123340.703f5c86@nehalam>
In-reply-To: <20091111123340.703f5c86@nehalam>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200911112234.24180.elendil@planet.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 828
Lines: 20

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/