From: Stephen Hemminger <shemminger@vyatta.com>
To: Frans Pop <elendil@planet.nl>
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: Mount -o sync regression in 2.6.31
Date: Wed, 11 Nov 2009 14:20:42 -0800 [thread overview]
Message-ID: <20091111142042.657c1a66@nehalam> (raw)
In-Reply-To: <200911112234.24180.elendil@planet.nl>
On Wed, 11 Nov 2009 22:34:22 +0100
Frans Pop <elendil@planet.nl> wrote:
> 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
That makes sense but is confusing.
--
next prev parent reply other threads:[~2009-11-11 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:33 Mount -o sync regression in 2.6.31 Stephen Hemminger
2009-11-11 21:34 ` Frans Pop
2009-11-11 22:20 ` Stephen Hemminger [this message]
2009-11-13 22:47 ` Stephen Hemminger
2009-11-13 23:07 ` Andrew Morton
2009-11-13 23:28 ` Stephen Hemminger
2009-11-17 0:04 ` [PATCH] ext2: clear uptodate flag on super block I/O error Stephen Hemminger
2009-11-17 2:08 ` Nick Piggin
2009-11-17 17:16 ` Stephen Hemminger
2009-11-14 13:18 ` Mount -o sync regression in 2.6.31 Frederic Weisbecker
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=20091111142042.657c1a66@nehalam \
--to=shemminger@vyatta.com \
--cc=elendil@planet.nl \
--cc=jens.axboe@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.