From: Mike Snitzer <snitzer@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, Alasdair G Kergon <agk@redhat.com>
Subject: Re: A BUG in snapshot merging
Date: Tue, 22 Sep 2009 13:00:00 -0400 [thread overview]
Message-ID: <20090922170000.GA1806@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909221130590.24935@hs20-bc2-1.build.redhat.com>
On Tue, Sep 22 2009 at 12:37pm -0400,
Mikulas Patocka <mpatocka@redhat.com> wrote:
> I got this BUG when attempting to use merged patchset of Mike's and Jon's
> patches (from
> http://people.redhat.com/msnitzer/patches/snapshot-merge/kernel_unified/2.6.31/)
>
> I think we shouldn't join these two patchsets together. I mean, before
> clustered patches, merging was stable (I reviewed and tested it and except
> for one userspace bug (already fixed) there were no flaws) ... now it
> doesn't work.
>
> I would recommend to leave merging as it was (i.e. stable, apply only
> little patches on it) and develop Jon's clustering on the top of merging
> and not interleave it with merging, so that the clustering patches could
> be rolled back if problems were found. When clustering will be stable and
> reviewed, it could be added to the kernel --- but it may happen later than
> merging, so don't mix it.
When did you pull in the patches on my people page?
As of yesterday evening (Boston) I uploaded patches that are broken
(based on Jon's reworked handover). I'm now combining your handover
with Jon's handover (in hopes of avoiding refactoring associations).
The patches are in flux... I'm working to resolve the issues that are
rooted at the handover mechanism.
As for patch ordering. I'm not opposed to what you suggested (merge
first then clusterized). But that is a secondary concern right now. We
have enough time between now and the next merge window to get them both
working.
Mike
next prev parent reply other threads:[~2009-09-22 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0909211349480.16230@hs20-bc2-1.build.redhat.com>
[not found] ` <20090921175655.GA28074@redhat.com>
[not found] ` <Pine.LNX.4.64.0909211815580.31653@hs20-bc2-1.build.redhat.com>
2009-09-22 16:37 ` A BUG in snapshot merging Mikulas Patocka
2009-09-22 17:00 ` Mike Snitzer [this message]
2009-09-22 19:20 ` Mike Snitzer
2009-09-24 0:07 ` Mike Snitzer
2009-09-24 6:33 ` Mike Snitzer
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=20090922170000.GA1806@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.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 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.