Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	mniederle-RbZlAiThDcE@public.gmane.org
Subject: Re: Which patches for 2.6.30
Date: Sat, 06 Jun 2009 03:32:21 +0900 (JST)	[thread overview]
Message-ID: <20090606.033221.18321078.ryusuke@osrg.net> (raw)
In-Reply-To: <20090605171027.176549f1@simplux>

Hi!
On Fri, 5 Jun 2009 17:10:27 +0200, "Michael Niederle" wrote:
> Hi!
>
> I want to use nilfs as the root file system of the next version of
> SIMPLUX (a Gentoo-Linux based distribution for pen-drives). Shutdown
> by now works cleanly.  (I had some troubles in the past ...)
> 
> My question is: Which patches do I need to include the most current
> version of nilfs in the upcoming final release of kernel 2.6.30?
> nilfs will be directly included in the kernel (no module). Is it
> possible to have a single patch that does it all?

Basically, you should use the in-tree version without applying any
additional patches because known bugfixes are included in the kernel
2.6.30 and the remaining patches are experimental.

But, you can try the latest version available on the experimental
branch or for-next branch in nilfs2.git:

 git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git

(As you can see in

 http://git.kernel.org/?p=linux/kernel/git/ryusuke/nilfs2.git;a=shortlog;h=experimental

 the for-next branch is included in the experimental branch)


If you already have a git clone of linus' tree, you can add those
branches like:

 $ cd linux-2.6
 $ git remote add nilfs2 git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
 $ git branch nilfs2-experimental nilfs2/experimental  (or nilfs2/for-next)
 $ git checkout nilfs2-experimental

Otherwise, you can get it directly by:

 $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
 $ cd nilfs2
 $ git checkout experimental

And, you can create the single patch by:

 $ cd nilfs2
 $ git diff master...experimental > ~/v2.6.30-nilfs2-experimental.diff


Note that the for-next branch and the experimental branch are
frequently "rebased" and this may confuse their existing branches.


Cheers,
Ryusuke Konishi

      reply	other threads:[~2009-06-05 18:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1244170801.2227.users@nilfs.org>
     [not found] ` <mailman.1.1244170801.2227.users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
2009-06-05 15:10   ` Which patches for 2.6.30 Michael Niederle
2009-06-05 18:32     ` Ryusuke Konishi [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=20090606.033221.18321078.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=mniederle-RbZlAiThDcE@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@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