From: Jeff Kirsher <tarbal@gmail.com>
To: Yinglin Sun <yinglin.s@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, sfr@canb.auug.org.au,
linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org,
sparclinux@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: moving GIT back to kernel.org...
Date: Sat, 08 Oct 2011 00:01:35 -0700 [thread overview]
Message-ID: <4E8FF54F.1080306@gmail.com> (raw)
In-Reply-To: <CAN17JHUGnAbHJmwybjJVdxq4JOgHfDxChw1P7q1yrkqH6Ci05w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 10/07/2011 11:55 PM, Yinglin Sun wrote:
> On Fri, Oct 7, 2011 at 12:59 PM, David Miller <davem@davemloft.net> wrote:
>> From: David Miller <davem@davemloft.net>
>> Date: Fri, 07 Oct 2011 14:57:03 -0400 (EDT)
>>
>>> I'm about to setup my GIT trees on kernel.org, once that is complete
>>> I will be solely updating those trees again.
>>>
>>> I will notify everyone when this is ready to go.
>>>
>>> Just a heads up for everyone...
>> Ok, they are now online, please update your URLs.
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc.git
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide.git
>>
> I'm still new to net kernel development, so a little confused about these trees.
> So we should submit patches based on these trees, instead of Linus'?
> About net and net-next, How to decide which one to use?
>
> Thanks!
>
> Yinglin
>
*If* you have change against the network core/drivers then, you would
want to use David Miller's net or net-next trees.
As a general rule:
- net tree is only for fixes/critical fixes
- net-next tree is for everything else
There are always exceptions, but if you stick to the above general rule,
you will be fine.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jeff Kirsher <tarbal@gmail.com>
To: Yinglin Sun <yinglin.s@gmail.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, sfr@canb.auug.org.au,
linux-wireless@vger.kernel.org, netfilter-devel@vger.kernel.org,
sparclinux@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: moving GIT back to kernel.org...
Date: Sat, 08 Oct 2011 07:01:35 +0000 [thread overview]
Message-ID: <4E8FF54F.1080306@gmail.com> (raw)
In-Reply-To: <CAN17JHUGnAbHJmwybjJVdxq4JOgHfDxChw1P7q1yrkqH6Ci05w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On 10/07/2011 11:55 PM, Yinglin Sun wrote:
> On Fri, Oct 7, 2011 at 12:59 PM, David Miller <davem@davemloft.net> wrote:
>> From: David Miller <davem@davemloft.net>
>> Date: Fri, 07 Oct 2011 14:57:03 -0400 (EDT)
>>
>>> I'm about to setup my GIT trees on kernel.org, once that is complete
>>> I will be solely updating those trees again.
>>>
>>> I will notify everyone when this is ready to go.
>>>
>>> Just a heads up for everyone...
>> Ok, they are now online, please update your URLs.
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc.git
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide.git
>>
> I'm still new to net kernel development, so a little confused about these trees.
> So we should submit patches based on these trees, instead of Linus'?
> About net and net-next, How to decide which one to use?
>
> Thanks!
>
> Yinglin
>
*If* you have change against the network core/drivers then, you would
want to use David Miller's net or net-next trees.
As a general rule:
- net tree is only for fixes/critical fixes
- net-next tree is for everything else
There are always exceptions, but if you stick to the above general rule,
you will be fine.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2011-10-08 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 18:57 moving GIT back to kernel.org David Miller
2011-10-07 18:57 ` David Miller
2011-10-07 19:59 ` David Miller
2011-10-07 19:59 ` David Miller
2011-10-07 22:42 ` Stephen Rothwell
2011-10-07 22:42 ` Stephen Rothwell
2011-10-07 22:46 ` David Miller
2011-10-07 22:46 ` David Miller
2011-10-07 23:10 ` Stephen Rothwell
2011-10-07 23:10 ` Stephen Rothwell
2011-10-08 6:55 ` Yinglin Sun
2011-10-08 6:55 ` Yinglin Sun
2011-10-08 7:01 ` Jeff Kirsher [this message]
2011-10-08 7:01 ` Jeff Kirsher
2011-10-08 7:09 ` Yinglin Sun
2011-10-08 7:09 ` Yinglin Sun
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=4E8FF54F.1080306@gmail.com \
--to=tarbal@gmail.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sparclinux@vger.kernel.org \
--cc=yinglin.s@gmail.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 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.