From: Linus Torvalds <torvalds@osdl.org>
To: Christian Kujau <evil@g-house.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops in 2.6.10-rc1
Date: Tue, 9 Nov 2004 16:23:08 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0411091621220.2301@ppc970.osdl.org> (raw)
In-Reply-To: <41915CE3.4080404@g-house.de>
On Wed, 10 Nov 2004, Christian Kujau wrote:
> >
> > bk set -n -d -r1.2462 -r1.2463 | bk -R prs -h -d'<:P:@:HOST:>\n$each(:C:){\t(:C:)\n}\n' -
> >
> > which is black magic that does a set operation and shows all the changes
> > in between the sets of "bk at 1.2462" and "bk at 1.2463".
>
> hm, i still fail to see the "magic" part here. from a current tree i get:
You don't see any magic, unless there are merges involved. And you've
already narrowed the thing down to a single non-merge changeset, at which
point the "magic" way is just a very slow way of doing the same thing.
The magic hits you only when you have non-trivial merges, in which case
the set operation shows you more than the "just walk from one top-of-tree
to the other".
Linus
next prev parent reply other threads:[~2004-11-10 0:23 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 13:12 Oops in 2.6.10-rc1 Christian
2004-10-28 13:29 ` [Alsa-devel] " Jaroslav Kysela
2004-10-28 14:09 ` Christian
2004-11-04 15:16 ` Christian Kujau
2004-11-05 2:35 ` Christian Kujau
2004-11-05 11:40 ` holborn
2004-11-07 1:24 ` Christian Kujau
2004-11-07 7:02 ` Linus Torvalds
2004-11-07 13:10 ` Christian Kujau
2004-11-07 16:02 ` Christian Kujau
2004-11-07 16:57 ` Linus Torvalds
2004-11-07 18:31 ` Christian Kujau
2004-11-07 18:44 ` Linus Torvalds
2004-11-07 23:45 ` Christian Kujau
2004-11-07 23:45 ` Christian Kujau
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 13:01 ` Christian Kujau
2004-11-08 13:01 ` Christian Kujau
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 20:59 ` Christian Kujau
2004-11-08 20:59 ` Christian Kujau
2004-11-08 23:49 ` Christian Kujau
2004-11-09 1:05 ` Linus Torvalds
2004-11-09 1:41 ` Christian Kujau
2004-11-09 1:31 ` Christian Kujau
2004-11-09 7:40 ` Pekka Enberg
2004-11-09 12:33 ` Christian Kujau
2004-11-09 17:26 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 18:53 ` Linus Torvalds
2004-11-09 19:04 ` [PATCH] kobject: fix double kobject_put() in error path of kobject_add() Greg KH
2004-11-09 19:08 ` Greg KH
2004-11-09 20:19 ` Pekka Enberg
2004-11-09 21:21 ` Christian Kujau
2004-11-09 21:31 ` Christian Kujau
2004-11-09 19:09 ` Linus Torvalds
2004-11-09 22:06 ` Christian Kujau
2004-11-09 23:30 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau
2004-11-09 23:40 ` Matt Domsch
2004-11-10 0:21 ` Christian Kujau
2004-11-10 1:01 ` Linus Torvalds
2004-11-11 22:43 ` Matt Domsch
2004-11-11 22:53 ` Linus Torvalds
2004-11-11 22:55 ` Matt Domsch
2004-11-12 0:27 ` Christian Kujau
2004-11-12 0:49 ` Linus Torvalds
2004-11-12 1:27 ` Christian Kujau
2004-11-10 0:12 ` Oops in 2.6.10-rc1 Christian Kujau
2004-11-10 0:23 ` Linus Torvalds [this message]
2004-11-08 18:44 ` Pekka Enberg
2004-11-08 18:44 ` Pekka Enberg
2004-11-08 19:00 ` Greg KH
2004-11-08 19:00 ` Greg KH
2004-11-08 19:18 ` Pekka Enberg
2004-11-08 19:18 ` Pekka Enberg
2004-11-08 19:30 ` Pekka Enberg
2004-11-08 19:30 ` Pekka Enberg
2004-11-08 20:31 ` Christian Kujau
2004-11-08 20:31 ` Christian Kujau
2004-11-07 13:05 ` Pekka Enberg
2004-11-07 13:43 ` Christian Kujau
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=Pine.LNX.4.58.0411091621220.2301@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=evil@g-house.de \
--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.