Is www.nilfs.org/git the development tree?

Is www.nilfs.org/git the development tree?

[Zhu Yanhai]

Hi,
Is www.nilfs.org/git the development tree? It seems really old, and
can't compile against v2.6.30 kernel.
If it's not, where is the development git repo for nilfs2?

Thanks,
Zhu Yanhai

Re: Is www.nilfs.org/git the development tree?

[Ryusuke Konishi]

Hi!
On Sat, 18 Jul 2009 00:00:02 +0800, Zhu Yanhai wrote:
> Hi,
> Is www.nilfs.org/git the development tree? It seems really old, and
> can't compile against v2.6.30 kernel.

The nilfs2-module.git in the site is the tree to maintain standalone
module for kernels prior to 2.6.30.

> If it's not, where is the development git repo for nilfs2?
> 

please see 

http://git.kernel.org/?p=linux/kernel/git/ryusuke/nilfs2.git;a=summary

for the development tree.

Note that the nilfs2.git is a tree to manage patchsets for the
mainline.  I mean its branches are frequently rebased; I recommend you
to use "git remote" if you follow the tree.

Here I address use of branches in the tree:

 o master - mainline

 o fixes - pending bugfixes

 o for-next - branch exported to linux-next
              (used for bonding test and compilation tests)

 o for-linus - this holds patches to be sent to Linus

 o experimental - branch to hold every patch including experimental
                  patches, or patches queued for next merge window.

> Thanks,
> Zhu Yanhai

Cheers,
Ryusuke Konishi

Re: Is www.nilfs.org/git the development tree?

[Zhu Yanhai]

Thanks a lot!

-Zhu Yanhai

2009/7/18 Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>:
> Hi!
> On Sat, 18 Jul 2009 00:00:02 +0800, Zhu Yanhai wrote:
>> Hi,
>> Is www.nilfs.org/git the development tree? It seems really old, and
>> can't compile against v2.6.30 kernel.
>
> The nilfs2-module.git in the site is the tree to maintain standalone
> module for kernels prior to 2.6.30.
>
>> If it's not, where is the development git repo for nilfs2?
>>
>
> please see
>
> http://git.kernel.org/?p=linux/kernel/git/ryusuke/nilfs2.git;a=summary
>
> for the development tree.
>
> Note that the nilfs2.git is a tree to manage patchsets for the
> mainline.  I mean its branches are frequently rebased; I recommend you
> to use "git remote" if you follow the tree.
>
> Here I address use of branches in the tree:
>
>  o master - mainline
>
>  o fixes - pending bugfixes
>
>  o for-next - branch exported to linux-next
>              (used for bonding test and compilation tests)
>
>  o for-linus - this holds patches to be sent to Linus
>
>  o experimental - branch to hold every patch including experimental
>                  patches, or patches queued for next merge window.
>
>> Thanks,
>> Zhu Yanhai
>
> Cheers,
> Ryusuke Konishi
>
>