From: "chen.mingzheng" <chen.mingzheng@outlook.com>
To: kernelnewbies@kernelnewbies.org
Subject: How to track the source tree of kernel
Date: Wed, 18 May 2022 22:47:59 +0800 [thread overview]
Message-ID: <TYCPR01MB5743A12014C751C230DCD57B81D19@TYCPR01MB5743.jpnprd01.prod.outlook.com> (raw)
Hi Guys,
Sorry to bother you all. I'm just starting learning linux with a rpi4b.
I found the raspi source tree have many branches, which are different
from the kernel source tree, which also have many branches. I want to
know how should I track the source code. should I track all branches
from the remote repo, or just stick to a specific branch? How did you do
so that you can catch up to lastest kernel?
Thanks in advance!
Sincerely,
A Linux newbies.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2022-05-18 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:47 chen.mingzheng [this message]
2022-05-18 15:17 ` How to track the source tree of kernel Greg KH
2022-05-19 11:14 ` 陈 明政
2022-05-19 14:53 ` Fox Chen
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=TYCPR01MB5743A12014C751C230DCD57B81D19@TYCPR01MB5743.jpnprd01.prod.outlook.com \
--to=chen.mingzheng@outlook.com \
--cc=kernelnewbies@kernelnewbies.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).