From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: linux-newbie@vger.kernel.org
Subject: Correlation between linux-2.6-stable kernel tree and linux-2.6.24.4.tar.bz2
Date: Wed, 02 Apr 2008 15:33:25 +0200 [thread overview]
Message-ID: <47F38B25.7050202@visionsystems.de> (raw)
Hi all,
I've recently checked the linux-2.6-stable kernel tree out
(http://git2.kernel.org/?p=linux/kernel/git/stable/linux-2.6-stable.git;a=summary).
During configuration I found out that some files are missing for example
arch/arm/mach-pxa/pxa300.c, arch/arm/mach-pxa/pxa320.c and so on. These
files are contained in the linux-2.6.24.4.tar.bz2. As as I understand
the linux-2.6-stable kernel tree reflects the latest stable kernel (i
this case 2.6.24.4). Why are these files missing? Where can I get info
about git kernel tree structure with verbose description of the git trees?
Best regards,
Yegor Yefremov
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
reply other threads:[~2008-04-02 13:33 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=47F38B25.7050202@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=linux-newbie@vger.kernel.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