From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
zhu.yanhai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Is www.nilfs.org/git the development tree?
Date: Sat, 18 Jul 2009 01:47:46 +0900 (JST) [thread overview]
Message-ID: <20090718.014746.73272641.ryusuke@osrg.net> (raw)
In-Reply-To: <977a2be20907170900u3c5e64e8ne9373ea100e8b16c-JsoAwUIsXosN+BqQ9rBEUg@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
next prev parent reply other threads:[~2009-07-17 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 16:00 Is www.nilfs.org/git the development tree? Zhu Yanhai
[not found] ` <977a2be20907170900u3c5e64e8ne9373ea100e8b16c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-17 16:47 ` Ryusuke Konishi [this message]
[not found] ` <20090718.014746.73272641.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-07-18 2:10 ` Zhu Yanhai
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=20090718.014746.73272641.ryusuke@osrg.net \
--to=ryusuke-sg5x7nla6pw@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
--cc=zhu.yanhai-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox