From: free.amit.kumar@gmail.com (Amit Kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Which repository to clone ?
Date: Wed, 1 Feb 2017 23:47:08 +0000 [thread overview]
Message-ID: <20170201234708.GA13053@li620-105.members.linode.com> (raw)
In-Reply-To: <CAB3L5oyR4EtmEjxFb3G_D-aJXxvhOjtKvO3COqMd8K6UOq+bSQ@mail.gmail.com>
On Thu, Feb 02, 2017 at 03:39:18AM +0530, srishti sharma wrote:
> Hey,
> I am an absolute newbie , I tried to clone greg kroah-hartman's
> staging tree repository , somehow I was not able to boot in the kernel
> I built .
>
> Also, Does this command below give me the latest kernel code ?
>
> I have tried to clone another repository using the command below
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
>
>
> while building with this , I had to install gcc plugin-dev . I don't
> understand why ?
> I didn't have to do it last time I built the kernel
You may use this link,
https://www.kernel.org/doc/man-pages/linux-next.html
In summary, first you clone main upstream tree then add linux-next tree.
Whenever you want to create a patch, create a topic branch from the
latest next-* tag.
Regards,
Amit Kumar
>
> Regards
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2017-02-01 23:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 22:09 Which repository to clone ? srishti sharma
2017-02-01 23:36 ` Lino Sanfilippo
2017-02-01 23:38 ` srishti sharma
2017-02-01 23:46 ` Lino Sanfilippo
2017-02-01 23:47 ` Amit Kumar [this message]
2017-02-01 23:58 ` srishti sharma
2017-02-02 0:05 ` srishti sharma
2017-02-02 3:29 ` Amit Kumar
2017-02-02 4:53 ` Amit Kumar
2017-02-02 7:12 ` Greg KH
2017-02-02 10:32 ` srishti sharma
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=20170201234708.GA13053@li620-105.members.linode.com \
--to=free.amit.kumar@gmail.com \
--cc=kernelnewbies@lists.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).