From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] add configure option --with-root-libdir
Date: Tue, 28 Aug 2018 10:25:11 -0400 [thread overview]
Message-ID: <20180828142511.GA19128@thunk.org> (raw)
In-Reply-To: <20180828071202.GA29049@jaegeuk-macbookpro.roam.corp.google.com>
On Tue, Aug 28, 2018 at 12:12:02AM -0700, Jaegeuk Kim wrote:
>
> I think f2fs-tools is getting much firmer lib APIs, so don't expect frequent
> major updates on library versions, but was struggling to keep it as much as
> possible tho. I'm checking the final test results, and thus, planning to
> release 1.11.1 within a week or so. In this release, I'm seeing that
> it requires to bump revision like libf2fs-5.1.0, and libf2fs-format-4.1.0.
Just checking to be sure --- does 5.1.0 mean that that were no changes
to interfaces that were already present in 5.0.0, but there are new
interfaces added? That's what a minor version bump generally means,
but I just want to be sure.
Thanks,
- Ted
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2018-08-28 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 3:04 [PATCH 1/2] add configure option --with-root-libdir Theodore Ts'o
2018-08-20 3:04 ` [PATCH 2/2] Ask git to ignore the generated sg_write_buffer executable Theodore Ts'o
2018-08-20 7:21 ` Chao Yu
2018-08-27 15:51 ` [PATCH 1/2] add configure option --with-root-libdir Theodore Y. Ts'o
2018-08-27 16:57 ` Jaegeuk Kim
2018-08-27 23:56 ` Theodore Y. Ts'o
2018-08-28 7:12 ` Jaegeuk Kim
2018-08-28 14:25 ` Theodore Y. Ts'o [this message]
2018-08-28 16:59 ` Jaegeuk Kim
2018-08-29 3:10 ` [PATCH 1/2] add cotnfigure " Theodore Y. Ts'o
2018-08-29 21:04 ` Jaegeuk Kim
2018-08-29 23:51 ` Theodore Y. Ts'o
2018-08-28 3:43 ` [PATCH 1/2] add configure " Chao Yu
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=20180828142511.GA19128@thunk.org \
--to=tytso@mit.edu \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).