Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: nickm-gdz6ECn1J1HQT0dZR+AlfA@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CentOS 5 support for nilfs
Date: Sun, 27 Jun 2010 00:24:13 +0900 (JST)	[thread overview]
Message-ID: <20100627.002413.27799974.ryusuke@osrg.net> (raw)
In-Reply-To: <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E52D-7hT9n0F4+5en5JXSkZkeBYboaULrDjGDrOgnGio5az8@public.gmane.org>

Hi,
On Sat, 26 Jun 2010 02:10:17 -0500, "Martin, Nick" wrote:
> Hello,		
> 
> I have been watching the list and web site for some time, hoping for an update to the CentOS 5 download.
> It does not yet include the utilities released on 10 April.

I'm using the following packages for the CentOS 5 series.
Or, do you have any problems for them ?

  http://www.nilfs.org/pub/centos/5/RPMS/i386/nilfs-utils-2.0.18-3.i386.rpm
  http://www.nilfs.org/pub/centos/5/RPMS/x86_64/nilfs-utils-2.0.18-3.x86_64.rpm

These include the release on April 10.

Regards,
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

  parent reply	other threads:[~2010-06-26 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 15:27 [PATCHv4 0/2] nilfs2: asynchronous sb update Jiro SEKIBA
     [not found] ` <1277393260-19835-1-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-06-24 15:27   ` [PATCHv4 1/2] nilfs2: introduce nilfs_prepare_super Jiro SEKIBA
2010-06-24 15:27   ` [PATCHv4 2/2] nilfs2: sync super blocks in turns Jiro SEKIBA
     [not found]     ` <1277393260-19835-3-git-send-email-jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
2010-06-25  9:06       ` Ryusuke Konishi
     [not found]         ` <20100625.180639.160014063.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-06-26  5:05           ` Jiro SEKIBA
     [not found]             ` <87zkyi1izo.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-06-26  7:10               ` CentOS 5 support for nilfs Martin, Nick
     [not found]                 ` <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E52D-7hT9n0F4+5en5JXSkZkeBYboaULrDjGDrOgnGio5az8@public.gmane.org>
2010-06-26 15:24                   ` Ryusuke Konishi [this message]
     [not found]                     ` <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E661@p3saturn.p3corpnet.pivot3.com>
     [not found]                       ` <A94BFDB17DC4E1478F7ACF6EBA3FD8234AE3F6E661-7hT9n0F4+5en5JXSkZkeBYboaULrDjGDrOgnGio5az8@public.gmane.org>
2010-06-29  5:59                         ` Ryusuke Konishi
2010-06-26 14:51               ` [PATCHv4 2/2] nilfs2: sync super blocks in turns Ryusuke Konishi
     [not found]                 ` <20100626.235108.163664714.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-06-27  3:22                   ` Jiro SEKIBA
     [not found]                     ` <87sk49dur6.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-06-28  2:35                       ` Ryusuke Konishi
2010-06-24 16:56   ` [PATCHv4 0/2] nilfs2: asynchronous sb update Ryusuke Konishi

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=20100627.002413.27799974.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nickm-gdz6ECn1J1HQT0dZR+AlfA@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