From: Jon Loeliger <jdl@freescale.com>
To: "Bizhan Gholikhamseh (bgholikh)" <bgholikh@cisco.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: Differences between git tree
Date: Wed, 02 Jan 2008 12:04:51 -0600 [thread overview]
Message-ID: <1199297091.7345.20.camel@ld0161-tx32> (raw)
In-Reply-To: <F795765B112E7344AF36AA911279641502D1A907@xmb-sjc-212.amer.cisco.com>
On Thu, 2007-12-20 at 07:11, Bizhan Gholikhamseh (bgholikh) wrote:
> Hi,
> Could someone let me know what is the each of these git tree are?
>
> http://opensource.freescale.com/pub/scm/linux-2.6-jdl.git
> AND
> http://www.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git
Hrm. I suppose I should answer that one...
Use Paul's tree from kernel.org.
My tree on opensource.freescale.com was my random patches
and crud, being published so others could get a hold of them.
Anything of value there has been moved or integrated into
Paul or Linus' tree by now.
HTH,
jdl
prev parent reply other threads:[~2008-01-02 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.56.1171312373.21008.linuxppc-embedded@ozlabs.org>
2007-12-20 13:11 ` Differences between git tree Bizhan Gholikhamseh (bgholikh)
2008-01-02 18:04 ` Jon Loeliger [this message]
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=1199297091.7345.20.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=bgholikh@cisco.com \
--cc=linuxppc-embedded@ozlabs.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).