linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Turritopsis Dohrnii Teo En Ming <teo.en.ming@protonmail.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Cc: "ceo@teo-en-ming-corp.com" <ceo@teo-en-ming-corp.com>
Subject: Re: What is the difference between linux-next and linux-kernel mailing lists?
Date: Thu, 22 Sep 2022 09:43:13 +0700	[thread overview]
Message-ID: <14fa2a39-b5e6-f878-2b87-2dd86b450920@gmail.com> (raw)
In-Reply-To: <3eqrFna3vX_qv5tM9LT_0Mqf7zyT1B5OPa8UcwIvO_CW9eFNly54zZmShglkINpHxXCNo-nDdeabRQ2VkPTwvizp_atYq7LsiuMKqGERug0=@protonmail.com>

On 9/16/22 21:25, Turritopsis Dohrnii Teo En Ming wrote:
> Subject: What is the difference between linux-next and linux-kernel mailing lists?
> 
> Good day from Singapore,
> 
> What is the difference between linux-next and linux-kernel mailing lists?
> 
> What goes into linux-next mailing list and what goes into linux-kernel mailing list?
> 

Hi,

LKML is mailing list for Linux kernel development. There, general discussions
as well as patch submissions and reviews take place.

linux-next mailing list is for linux-next tree, where all subsystems tree
are merged (excluding stable kernel tree). It is a snapshot for what next
kernel release will look like.

If you'd like to contribute, see Documentation/process/submitting-patches.rst.

And don't forget DON'T top post; reply inline instead.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

      reply	other threads:[~2022-09-22  2:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 14:25 What is the difference between linux-next and linux-kernel mailing lists? Turritopsis Dohrnii Teo En Ming
2022-09-22  2:43 ` Bagas Sanjaya [this message]

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=14fa2a39-b5e6-f878-2b87-2dd86b450920@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=ceo@teo-en-ming-corp.com \
    --cc=linux-next@vger.kernel.org \
    --cc=teo.en.ming@protonmail.com \
    /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).