Linux NILFS development
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] nilfs2 fixes for 3.0-rc3
Date: Mon, 13 Jun 2011 16:22:01 +0200	[thread overview]
Message-ID: <201106131622.01637.dexen.devries@gmail.com> (raw)
In-Reply-To: <20110613.203039.16056005.ryusuke-sG5X7nlA6pw@public.gmane.org>

On Monday 13 of June 2011 13:30:39 you wrote:
> > 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.


thanks for clarification; turns out I've mixed up branches in my local repo.


-- 
dexen deVries

[[[↓][→]]]

For example, if the first thing in the file is:
   <?kzy irefvba="1.0" rapbqvat="ebg13"?>
an XML parser will recognize that the document is stored in the traditional 
ROT13 encoding.

(( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))
--
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

      parent reply	other threads:[~2011-06-13 14:22 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
     [not found]         ` <20110613.203039.16056005.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-06-13 14:22           ` dexen deVries [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=201106131622.01637.dexen.devries@gmail.com \
    --to=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