From: Greg KH <greg@kroah.com>
To: "chen.mingzheng" <chen.mingzheng@outlook.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: How to track the source tree of kernel
Date: Wed, 18 May 2022 17:17:28 +0200 [thread overview]
Message-ID: <YoUOCCm8d/p8JYfx@kroah.com> (raw)
In-Reply-To: <TYCPR01MB5743A12014C751C230DCD57B81D19@TYCPR01MB5743.jpnprd01.prod.outlook.com>
On Wed, May 18, 2022 at 10:47:59PM +0800, chen.mingzheng wrote:
> 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?
It all depends on what you want to do as to what tree/branch to work off
of and to track.
So, what exactly do you want to do?
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2022-05-18 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:47 How to track the source tree of kernel chen.mingzheng
2022-05-18 15:17 ` Greg KH [this message]
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=YoUOCCm8d/p8JYfx@kroah.com \
--to=greg@kroah.com \
--cc=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).