All of lore.kernel.org
 help / color / mirror / Atom feed
From: luisbg@osg.samsung.com (Luis de Bethencourt)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Work with correct branch for kernel changes
Date: Sun, 13 Dec 2015 01:01:43 +0000	[thread overview]
Message-ID: <566CC377.9070708@osg.samsung.com> (raw)
In-Reply-To: <566c86d8.8956620a.5b12f.ffffa39c@mx.google.com>

On 12/12/15 20:43, Shirish Gajera wrote:
> Hi,
> 
> I am new to linux kernel and trying to understand  the process of
> different git branch to work.
> 
> So, if I am not wrong then there are different branch like stable, next,
> staging etc. Previously I work with staging branch so if I am making
> any changes for drivers/staging I have to work with staging branch like
> follow.
> git clone 
> git checkout -t -b staging-testing origin/staging-testing
> git chekcout -b MY_LOCAL_BRANCH
> not do work and subimt
> 
> So, how it work for other source structure, like now I want to make some
> for y2038 -> drivers/scsi which branch should I set up and work with,
> next/stable/or is there any specific y2038 branch.
> 
> Any wiki link or documentation that explain this full process which
> branch to work with when making changes to specific directory will be
> useful.
> 
> Thanks,
> Shirish
> 

Hi Shirish,

linux-next [0] is good to follow, and useful if you are touching cross-system
code. If you want to be safe, since not all subsystems are merged into
linux-next and some have multiple branches for next version fixes, new
features, etc, check the MAINTAINERS file [1]. There you will see information
you need.

For example for ACPI (drivers/acpi) it is
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm

I hope that clarifies your question.
Luis



[0] git clone https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
[1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS

  reply	other threads:[~2015-12-13  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 20:43 Work with correct branch for kernel changes Shirish Gajera
2015-12-13  1:01 ` Luis de Bethencourt [this message]
2015-12-17  9:04 ` Andrey Skvortsov

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=566CC377.9070708@osg.samsung.com \
    --to=luisbg@osg.samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.