From: Gary Thomas <gary@mlbassoc.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Kernel versions
Date: 03 Oct 2003 17:36:11 -0600 [thread overview]
Message-ID: <1065224171.18201.805.camel@hermes> (raw)
In-Reply-To: <20031003151729.GC21468@ip68-0-152-218.tc.ph.cox.net>
Tom,
For more than a year now, I've been working from the linuxppc_2_4_devel
tree, sending updates which have been merged in, etc. I just looked at
the recently discussed 2.4 tree (http://ppc.bkbits.net:8080/linuxppc-2.4)
and I see none of this work present.
So my questions are:
* What is the "proper" tree to be working from (2.4, 2.6)?
* What is the merge path from the work in 2_4_devel to these other trees?
... I wouldn't want all of my efforts to just get lost.
Thanks.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-10-03 23:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000e01c388dc$eb525510$0202a8c0@homevl9biy3v7e>
2003-10-02 12:17 ` Queston about Walnut Wolfgang Denk
2003-10-03 1:18 ` Jacky Lam
[not found] ` <3F7D3238.2090400@bluewin.ch>
2003-10-03 9:40 ` Jacky Lam
2003-10-03 15:07 ` Matt Porter
2003-10-03 16:34 ` Jacky Lam
2003-10-04 16:07 ` Matt Porter
2003-10-03 16:10 ` Dan Kegel
2003-10-03 16:45 ` Jacky Lam
2003-10-03 17:31 ` Dan Kegel
[not found] ` <20031003151729.GC21468@ip68-0-152-218.tc.ph.cox.net>
2003-10-03 23:36 ` Gary Thomas [this message]
2003-10-07 13:37 ` Kernel versions Tom Rini
2003-10-03 4:11 ` Queston about Walnut Jacky Lam
2003-10-03 7:44 ` Jacky Lam
2004-07-02 13:11 Kernel versions linuxppc
2004-07-02 14:29 ` Giuliano Pochini
2004-07-02 14:54 ` Wolfgang Denk
2004-07-02 15:37 ` Giuliano Pochini
2004-07-02 15:56 ` Gary Thomas
2004-07-06 15:08 ` Benjamin Herrenschmidt
2004-08-13 16:59 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2017-03-08 20:52 kernel versions Tobin C. Harding
2017-03-09 23:48 ` Daniel Axtens
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=1065224171.18201.805.camel@hermes \
--to=gary@mlbassoc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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).