From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Larry McVoy <lm@bitmover.com>,
Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] struct page, new bk tree
Date: Wed, 20 Feb 2002 15:26:36 -0500 [thread overview]
Message-ID: <3C74067C.EE824444@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0202192044140.7820-100000@imladris.surriel.com> <20020219155706.H26350@work.bitmover.com> <20020220201716.45A574E2E@oscar.casa.dyndns.org>
Ed Tomlinson wrote:
>
> In my opinion the idea of cset -x (while usefull) is fundamentally
> broken. The result of this is that ideas like blacklist need to be
> considered. I would propose instead an undo -x, that would
> generate a cset to reverse the one following the -x. This might
> lead to conflicts - these would be resolved the normal bk fashion.
> If bk handled ¯bad¯ csets in this manner there would be no need for
> blacklists - it is more robust in that you can always used undo -x.
Well, if the changes are properly split up, you shouldn't need to do
this... In the ideal situation it is easiest for Linus to accept or
reject a "bk pull" in its entirety. Then he can just do a "bk unpull"
Jeff
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ed Tomlinson <tomlins@cam.org>
Cc: Larry McVoy <lm@bitmover.com>,
Rik van Riel <riel@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] struct page, new bk tree
Date: Wed, 20 Feb 2002 15:26:36 -0500 [thread overview]
Message-ID: <3C74067C.EE824444@mandrakesoft.com> (raw)
In-Reply-To: 20020220201716.45A574E2E@oscar.casa.dyndns.org
Ed Tomlinson wrote:
>
> In my opinion the idea of cset -x (while usefull) is fundamentally
> broken. The result of this is that ideas like blacklist need to be
> considered. I would propose instead an undo -x, that would
> generate a cset to reverse the one following the -x. This might
> lead to conflicts - these would be resolved the normal bk fashion.
> If bk handled ?bad? csets in this manner there would be no need for
> blacklists - it is more robust in that you can always used undo -x.
Well, if the changes are properly split up, you shouldn't need to do
this... In the ideal situation it is easiest for Linus to accept or
reject a "bk pull" in its entirety. Then he can just do a "bk unpull"
Jeff
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-02-20 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 23:47 [PATCH] struct page, new bk tree Rik van Riel
2002-02-19 23:47 ` Rik van Riel
2002-02-19 23:57 ` Larry McVoy
2002-02-19 23:57 ` Larry McVoy
2002-02-20 19:07 ` Andreas Dilger
2002-02-20 19:07 ` Andreas Dilger
2002-02-20 19:27 ` Rik van Riel
2002-02-20 19:27 ` Rik van Riel
2002-02-20 20:17 ` Ed Tomlinson
2002-02-20 20:17 ` Ed Tomlinson
2002-02-20 20:26 ` Jeff Garzik [this message]
2002-02-20 20:26 ` Jeff Garzik
2002-02-20 20:31 ` Larry McVoy
2002-02-20 20:31 ` Larry McVoy
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=3C74067C.EE824444@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lm@bitmover.com \
--cc=riel@conectiva.com.br \
--cc=tomlins@cam.org \
--cc=torvalds@transmeta.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.