Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
To: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org
Cc: konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org,
	linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: nilfs2-utils ver 2.0.21?
Date: Fri, 21 Jan 2011 20:13:16 +0900 (JST)	[thread overview]
Message-ID: <20110121.201316.98061220.ryusuke@osrg.net> (raw)
In-Reply-To: <87k4i03vhx.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>

On Thu, 20 Jan 2011 16:05:46 +0900, Jiro SEKIBA wrote:
> 
> At Thu, 20 Jan 2011 15:49:49 +0900 (JST),
> Ryusuke Konishi wrote:
> > 
> > Hi,
> > On Thu, 20 Jan 2011 14:57:52 +0900, Jiro SEKIBA wrote:
> > > Hi,
> > > 
> > > Is there any plan to release nilfs2-utils v2.0.21 ?
> > > 
> > > It has been 4 months since v2.0.20 released.
> > > 
> > > The license of the library is properly changed to LGPL.
> > > So wouldn't it be a good reason to release the newer version?
> > 
> > Right, and looking back it should have been released last year after
> > the license migration was done.
> > 
> > > By the way, if I remember correctly, disk format won't change without
> > > breaking compatibility.  If it's the case, the warning when mounting
> > > nilfs2 partition may not need anymore?  It's scary anyway..
> > > http://www.spinics.net/lists/linux-nilfs/msg00595.html
> > > 
> > > thanks
> > 
> > The warning message is already taken away from the latest tree on
> > nilfs-utils.git, but we haven't yet made a release of it.
> > 
> > Okay, I will do a 2.0.21 later this week.
> 
> That would be great!
> 
> Thanks!
> 
> regards,

I've just put out nilfs-utils-2.0.21.  Finally, the warning was gone
:)

Thanks,
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:[~2011-01-21 11:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20  5:57 nilfs2-utils ver 2.0.21? Jiro SEKIBA
     [not found] ` <87mxmwxgkf.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2011-01-20  6:49   ` Ryusuke Konishi
     [not found]     ` <20110120.154949.93449454.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-01-20  7:05       ` Jiro SEKIBA
     [not found]         ` <87k4i03vhx.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2011-01-21 11:13           ` 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=20110121.201316.98061220.ryusuke@osrg.net \
    --to=konishi.ryusuke-zyj7fxus5i5l9jvzuh4aog@public.gmane.org \
    --cc=jir-hfpbi5WX9J54Eiagz67IpQ@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