From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] nilfs2 fixes for 3.0-rc3
Date: Mon, 13 Jun 2011 20:30:39 +0900 (JST) [thread overview]
Message-ID: <20110613.203039.16056005.ryusuke@osrg.net> (raw)
In-Reply-To: <201106131039.43298.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, 13 Jun 2011 10:39:42 +0200, dexen deVries wrote:
> Hi Ryusuke,
>
>
> On Monday 13 of June 2011 06:16:59 you wrote:
> > Hi Linus,
> >
> > please pull from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
> > for-linus
> >
> > to receive the following bug fixes. These fix a reported bug and two
> > boundary condition bugs recently found in btree code.
> >
> > Thanks,
> >
> > Ryusuke Konishi
> > --
> > The following changes since commit
> > 59c5f46fbe01a00eedf54a23789634438bb80603:
> >
> > Linux 3.0-rc2 (2011-06-06 18:06:33 +0900)
> >
> > are available in the git repository at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git
> > for-linus
> >
> > Ryusuke Konishi (3):
> > nilfs2: fix incorrect block address termination in node concatenation
> > nilfs2: fix missing block address termination in btree node shrinking
> > nilfs2: fix problem in setting checkpoint interval
>
>
> it seems only two of the above commits were pulled; the ``fix problem in
> setting checkpoint interval'' is missing from Linus' repo as of now.
Linus has not yet pulled any commits.
Just wait a day or so.
Ryusuke Konishi
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-13 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 4:16 [GIT PULL] nilfs2 fixes for 3.0-rc3 Ryusuke Konishi
[not found] ` <20110613.131659.170025547.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-13 8:39 ` dexen deVries
[not found] ` <201106131039.43298.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-06-13 11:30 ` Ryusuke Konishi [this message]
[not found] ` <20110613.203039.16056005.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-13 14:22 ` dexen deVries
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=20110613.203039.16056005.ryusuke@osrg.net \
--to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
--cc=dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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