From: Dan Malek <dan@embeddededge.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: still not clear on which tree to be using these days
Date: Fri, 25 Mar 2005 16:52:05 -0500 [thread overview]
Message-ID: <3787fed579cbb8849677a0baa10e0ee4@embeddededge.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0503251617100.15647@localhost.localdomain>
On Mar 25, 2005, at 4:19 PM, Robert P. J. Day wrote:
> what is the proper tree to be using these days for a 2.6 kernel on
> 8xx? for the longest time, i've used the "bk" checkout from
> bkbits.net, but i see others now working with what looks like the
> latest stock 2.6.x release.
I just use the latest kernel.org tree for everything. If I'm submitting
a patch, or working with someone else, I use the bk tree just to
be that little more up to date.
-- Dan
next prev parent reply other threads:[~2005-03-25 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-25 21:19 still not clear on which tree to be using these days Robert P. J. Day
2005-03-25 21:52 ` Dan Malek [this message]
2005-03-25 22:11 ` Robert P. J. Day
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=3787fed579cbb8849677a0baa10e0ee4@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.com \
/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).