All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Larry McVoy <lm@bitmover.com>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.5 development
Date: Fri, 15 Feb 2002 11:50:16 -0700	[thread overview]
Message-ID: <20020215185016.GQ2004@opus.bloom.county> (raw)
In-Reply-To: <20020215104433.C28735@work.bitmover.com>


On Fri, Feb 15, 2002 at 10:44:33AM -0800, Larry McVoy wrote:
> > These are related trees.  For 2.5.x all of the PPC trees are related to
> > the official Linus 2.5.x bk tree.  Something like:
> > linux-2.5 -> {for-linus-*, linuxppc-2.5}.
> > Since linuxppc-2.5 and for-linus-ppc are both children of linux-2.5,
> > shouldn't they be related?
>
> Yes, if they are all clones from the same original tree, they are all
> related.  The way to tell is to run "bk identity" in each tree, if that
> output is the same, you may pull between them.
>
> I thought Paul was talking about taking changes from the tree Cort created
> and putting it the tree Linus created.

Nope.  We're still using those for 2.2 and 2.4, but the official tree
for 2.5 (since it makes our lives easier too :))

So are out of order changesets on the horizon?

--
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-15 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 12:11 2.5 development Paul Mackerras
2002-02-15 16:40 ` Tom Rini
2002-02-15 16:58 ` Larry McVoy
2002-02-15 17:01   ` Jeff Garzik
2002-02-15 17:06     ` Larry McVoy
2002-02-15 17:17     ` Larry McVoy
2002-02-15 17:32   ` Tom Rini
2002-02-15 17:33     ` Larry McVoy
2002-02-15 17:36       ` Tom Rini
2002-02-15 18:44         ` Larry McVoy
2002-02-15 18:50           ` Tom Rini [this message]
2002-02-15 23:53             ` Larry McVoy
     [not found] <p05100300b8a144d7cf05@[66.26.75.241]>
2002-02-26 15:51 ` Stefan Jeglinski
2002-02-26 16:13   ` Tom Rini

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=20020215185016.GQ2004@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=lm@bitmover.com \
    --cc=paulus@samba.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.