From: Tom Rini <trini@kernel.crashing.org>
To: yellowdog-devel@lists.yellowdoglinux.org,
linuxppc-dev@lists.linuxppc.org, debian-powerpc@lists.debian.org
Subject: Important things about 'linuxppc_2_4' tree.
Date: Thu, 21 Feb 2002 15:10:32 -0700 [thread overview]
Message-ID: <20020221221032.GH719@opus.bloom.county> (raw)
As some of you might have noticed, the linuxppc_2_4 tree has been a bit
weird of late. The short version of it is that the "current"
linuxppc_2_4, as of (Thu, 21 Feb 2002 13:48:57 -0700) will export very
broken trees. The only good way to fix this is to just forget it
happened, and go back to an older clone.
First, the linuxppc_2_4_devel tree is _NOT_ effected. If you're only
using this, you're fine.
Second, if you have a copy of this tree and haven't done any local
modifications you can either find the changeset (It's:
"ChangeSet@1.543.1.41, 2002-02-17 09:38:20-07:00, trini@opus.bloom.county"
locally, probably different elsewhere) and do a bk clone -r REV .
../linuxppc_2_4-good, and then rm your old tree. Or you can just rm and
reclone.
If you've done modifications locally, you will need to do something like
the above clone -r'ing, and if you've checked in changes since then, bk
export -tpatch from your old repo, and bk import -tpatch ../patch . to
your new repo.
Sorry for the inconvenience.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-02-21 22:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020221221032.GH719@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=yellowdog-devel@lists.yellowdoglinux.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