From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 1F90DC433EF for ; Wed, 18 May 2022 15:18:08 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nrLQi-0003uU-J5; Wed, 18 May 2022 11:17:40 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nrLQf-0003tp-1D for kernelnewbies@kernelnewbies.org; Wed, 18 May 2022 11:17:37 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id CEE505C00D7; Wed, 18 May 2022 11:17:30 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 18 May 2022 11:17:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1652887050; x=1652973450; bh=9rO4vwtIii KaUup4s9TbV99K04YwNznbOiMQWrgBd1s=; b=UzaH3qFAC4HayeH5x2nwqcwbdM Tj4t09QH2Na9m8bsFPWpm4N1eVy7iFg7IKivWqcspGxwurtwrl3xVgPsmfeGuNr1 Dl7MwvmAkuImfK4sv1CJuR2hT4XgQ2isyVk7vl4KSDrH7E1Yc7U9+EcaNRhvApYh z+LAhYEe2x14SE5gDaCaf3wXEh+KkGPsBh5mRGSDIV/kef7O/rXWDDSdrtFGjX2j wnTh+juKQl6Rw9ifYHLQHr/Nu9iuWuq2q86osOAjlocogDC8/4vur3PfwgQVLIYM 4o01xs3N+yudckdwbo9TwgJ3ww1lMNEO8cqTLOOoPozFnhXAROvpgv+FmpyQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1652887050; x=1652973450; bh=9rO4vwtIiiKaUup4s9TbV99K04Yw NznbOiMQWrgBd1s=; b=UrlZJUeAwlx5SlK0fjxyDQoSmzcS+3Hc3w3hlOQbEWDB km398rZ8zv3HFcYm0o1Sa6AVbkpQjgxQY3tKv1ZdGEghzFpE5vYBjR1fxJg5q2Em UXupwaJkrHrjuo14TUCvfmDtjczPVpYDkuxAiCJ6Zuue2wjh1j79EiHPB4hQlD8o Xq6fuxJxA5owyiz5zwkQAIfIx8mr0CRkmQOH6bzIoQXsXBv5ybw2q+1QiEfq0N/W PWEgS1+dmwV9Cvv9vmWCJ0qcIw7K256Z/sgz2RerAkp8IYKMUyvt/WZ9GivKPHIW NCKQI4Zhmk1g409XrFNOsJ8JLTITzzR54lsH7em2Nw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrheelgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvfevuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheq necuggftrfgrthhtvghrnhepheegvdevvdeljeeugfdtudduhfekledtiefhveejkeejue fhtdeufefhgfehkeetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Feedback-ID: i787e41f1:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 18 May 2022 11:17:30 -0400 (EDT) Date: Wed, 18 May 2022 17:17:28 +0200 From: Greg KH To: "chen.mingzheng" Subject: Re: How to track the source tree of kernel Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org 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