From: Tom Rini <trini@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
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 08:08:03 -0700 [thread overview]
Message-ID: <20020412150803.GO759@opus.bloom.county> (raw)
In-Reply-To: <20020412133332.AA7E211258@denx.denx.de>
On Fri, Apr 12, 2002 at 03:33:27PM +0200, Wolfgang Denk wrote:
> In message <3CB6A2FE.62FFB14E@imc-berlin.de> you wrote:
> >
> > But I am still not sure if I understand what that means. Is there a
> > FAQ/README/HowTo about the LinuxPPC/Bitkeeper/Versionnumbering
> > somewhere?
>
> Good question!
Without a real answer, unfortunatly.
> > Which ChangeSet or Tag stands for a stable PPC kernel?
>
> Define stable :-(
Well, whichever ChangeSet is the merge of someplace:/.../linux_2_4 into
someplace:/.../linuxppc_2_4 is the merge into linuxppc_2_4.
> > Which ChangeSet equals (with regard to functionality) the official
> > linux-2.4.18 from kernel.org?
> >
> > Does the ChangesSet 1.900 (which is shortly after Tag 2.4.18) contain
> > all the stuff that's in the offical kernel?
>
> 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.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-04-12 15:08 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 [this message]
2002-04-12 15:13 ` Steven Scholz
2002-04-12 15:25 ` Tom Rini
2002-04-12 15:25 ` Wolfgang Denk
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=20020412150803.GO759@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
--cc=wd@denx.de \
/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.