From: andrej.skvortzov@gmail.com (Andrey Skvortsov)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Work with correct branch for kernel changes
Date: Thu, 17 Dec 2015 12:04:05 +0300 [thread overview]
Message-ID: <20151217090405.GD5422@localhost.localdomain> (raw)
In-Reply-To: <566c86d8.8956620a.5b12f.ffffa39c@mx.google.com>
On 12 Dec, 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
There are not only different branches, but also different git trees,
where development for different subsystem takes place usually.
I recommend you to watch this presentation of GregKH. He explains very
good, how the development is working.
https://kernel-recipes.org/en/2014/the-linux-kernel-how-fast-it-is-developed-and-how-we-stay-sane-doing-it/
--
Best regards,
Andrey Skvortsov
Secure eMail with gnupg: See http://www.gnupg.org/
PGP Key ID: 0x57A3AEAD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20151217/341b5af2/attachment.bin
prev parent reply other threads:[~2015-12-17 9:04 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
2015-12-17 9:04 ` Andrey Skvortsov [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=20151217090405.GD5422@localhost.localdomain \
--to=andrej.skvortzov@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 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.