From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: sporadic kernel panic during boot (MPC8xx, FEC)
Date: Fri, 12 Apr 2002 17:25:54 +0200 [thread overview]
Message-ID: <20020412152559.DBE0A1125A@denx.denx.de> (raw)
In-Reply-To: Your message of "Fri, 12 Apr 2002 08:08:03 PDT." <20020412150803.GO759@opus.bloom.county>
In message <20020412150803.GO759@opus.bloom.county> you wrote:
>
> > Another "interesting" question: assuming I identif a certain state of
> > the tree with Changeset XXX today, how can I find exactly the same
> > state XXX in three monbths, when the changesets may have been
> > renumbered?
>
> Well, ChangeSet 1.900 just happens to be after, but I don't recall the
> exact changeset of the 2.4.18 merge. As for the other question, I
> forget the exact command (ask on the bk users list) bk each ChangeSet
> has a unique key with it, that does not change, so you can later find
> things based on the key.
I know how to find the key:
$ bk prs -d ':KEY:\n' -r1.900 ChangeSet
======== ChangeSet 1.900 ========
trini@opus.bloom.county|ChangeSet|20020227003717|01133
I _think_ I should be able to perform the reverse operation using "bk
key2rev", but I never understood how to use this command.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
There's nothing disgusting about it [the Companion]. It's just
another life form, that's all. You get used to those things.
-- McCoy, "Metamorphosis", stardate 3219.8
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-12 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 7:07 sporadic kernel panic during boot (MPC8xx, FEC) Steven Scholz
2002-04-11 7:18 ` Christian Pellegrin
2002-04-11 7:23 ` Steven Scholz
2002-04-11 7:27 ` Christian Pellegrin
2002-04-11 15:31 ` Tom Rini
2002-04-11 15:41 ` Steven Scholz
2002-04-11 19:06 ` Wolfgang Grandegger
2002-04-11 19:12 ` Tom Rini
2002-04-12 9:03 ` Steven Scholz
2002-04-12 13:33 ` Wolfgang Denk
2002-04-12 15:08 ` Tom Rini
2002-04-12 15:13 ` Steven Scholz
2002-04-12 15:25 ` Tom Rini
2002-04-12 15:25 ` Wolfgang Denk [this message]
2002-04-12 17:13 ` Tom Rini
2002-04-11 7:27 ` Wolfgang Grandegger
2002-04-11 13:00 ` Steven Scholz
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 10:00 Kári Davíðsson
2002-04-11 13:03 ` Steven Scholz
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=20020412152559.DBE0A1125A@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).