kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: Richard Sailer <richard_siegfried@systemli.org>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Are kernel trees the same as a branch in terms of git?
Date: Mon, 13 Jul 2020 01:11:28 +0200	[thread overview]
Message-ID: <1453d6ed-5cb4-8f5d-9738-267ca3f26d93@systemli.org> (raw)
In-Reply-To: <CABfRCzjdOju402=zE_1xdXUaGVQvSiy2fVAn7zicx2x39sDJjA@mail.gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 837 bytes --]



On 10/07/2020 06:48, CRISTIAN ANDRES VARGAS GONZALEZ wrote:
> Hi guys, there is something I want to know, in the Linux kernel mailing
> list some developers refer to URLs like these tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master.
> 
> I doubt that in my learning about git I have not seen any source code
> called tree
> so I want to know if a kernel tree is a branch? very thanks :)

Hi,
In the way the linux kernel is developed every "branch" is a own repo.
Here branches are own repos like "net" , "net-next" or "alsa" with own
maintainers and own mailing list. Think of them like different
subdivisions in a company (also sometimes called "branch"). In most
cases these "branches" are own repos, not "git branches". I know it's a
bit confusing at first

Cheers,
-- Richard


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-07-12 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  4:48 Are kernel trees the same as a branch in terms of git? CRISTIAN ANDRES VARGAS GONZALEZ
2020-07-12 23:11 ` Richard Sailer [this message]
     [not found] <9F49A397-42B8-4E21-9E08-9C0B5A93C5F7@hxcore.ol>
2020-07-13  2:05 ` cristian andres vargas gonzalez

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=1453d6ed-5cb4-8f5d-9738-267ca3f26d93@systemli.org \
    --to=richard_siegfried@systemli.org \
    --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).