From: Helge Hafting <helge.hafting@hist.no>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Andy Isaacson <adi@hexapodia.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
"Mr. Berkley Shands" <berkley@cse.wustl.edu>,
linux-kernel@vger.kernel.org
Subject: Re: Severe I/O performance regression 2.6.6 to 2.6.7 or 2.6.8-rc3
Date: Fri, 06 Aug 2004 10:33:54 +0200 [thread overview]
Message-ID: <41134272.3080902@hist.no> (raw)
In-Reply-To: <20040806022734.GN17188@holomorphy.com>
William Lee Irwin III wrote:
>At some point in the past, I wrote:
>
>>-r+ -d:KEY: > key-bk$X" when it creates the tarball. Then anyone can
>>"bk clone -r`cat key-bk7` linux-2.5 linux-2.6-bk7" and duplicate the
>>-bk7 state of the tree, and then "bk changes -L ../linux-2.6-bk6" to
>>find the list of changesets differing.
>>
>>
>
>Once we get there, there must be some way to construct intermediate
>points between those two faithful at the very least to the snapshot
>ordering if not true chronological ordering.
>
>
You don't really need chronology for a binary search. With a
list of changesets, just apply/back out half of them. Divide the lot
any way you like, perhaps starting with only the "suspected" ones.
Helge Hafting
next prev parent reply other threads:[~2004-08-06 8:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 17:02 Severe I/O performance regression 2.6.6 to 2.6.7 or 2.6.8-rc3 Mr. Berkley Shands
2004-08-05 17:25 ` William Lee Irwin III
2004-08-05 19:58 ` Mr. Berkley Shands
2004-08-05 20:46 ` William Lee Irwin III
2004-08-05 22:33 ` Marcelo Tosatti
2004-08-06 0:21 ` William Lee Irwin III
2004-08-06 2:09 ` Andy Isaacson
2004-08-06 2:27 ` William Lee Irwin III
2004-08-06 2:42 ` Andy Isaacson
2004-08-06 3:11 ` William Lee Irwin III
2004-08-06 8:33 ` Helge Hafting [this message]
2004-08-06 8:51 ` William Lee Irwin III
2004-08-06 18:02 ` Fast patch for " Mr. Berkley Shands
2004-08-08 8:22 ` Ram Pai
2004-08-16 20:30 ` [PATCH] " Ram Pai
-- strict thread matches above, loose matches on Subject: below --
2004-08-06 0:41 Berkley Shands
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=41134272.3080902@hist.no \
--to=helge.hafting@hist.no \
--cc=adi@hexapodia.org \
--cc=berkley@cse.wustl.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=wli@holomorphy.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox