From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Goldwyn Rodrigues'" <rgoldwyn@suse.de>
Cc: "'LKML'" <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>,
"'Hyunchul Lee'" <hyc.lee@gmail.com>,
"'Eric Sandeen'" <sandeen@sandeen.net>,
"'Sedat Dilek'" <sedat.dilek@gmail.com>
Subject: RE: [ANNOUNCE] exfatprogs-1.0.2 version released
Date: Fri, 24 Apr 2020 08:38:58 +0900 [thread overview]
Message-ID: <000101d619c8$5c6e3b90$154ab2b0$@samsung.com> (raw)
In-Reply-To: <20200423144411.hmby6ux2utdrqsls@fiona>
> Hi Namjae,
Hi Goldwyn,
>
> On 17:49 23/04, Namjae Jeon wrote:
> > This is the second release of exfatprogs since the initial version(1.0.1).
> > We have received various feedbacks and patches since the previous
> > release and applied them in this release. Thanks for feedback and patches!
> >
> > According to Goldwyn's comments, We renamed the project name from
> > exfat-utils to exfatprogs. However, There is an opinion that just
> > renaming the name is not enough. Because the binary names(mkfs.exfat,
> > fsck.exfat) still are same with ones in current exfat-utils RPM package.
> >
> > If that's real problem, We are considering a long jump with 2.0.0 when
> > adding repair feature.
> >
> > Any feedback is welcome!:)
>
> I agree with Eric. We can add "Conflicts" flag to make sure there are conflicting capabilities in
> packages.
Okay.
>
> >
> > The major changes in this release:
> > * Rename project name to exfatprogs.
> > * label.exfat: Add support for label.exfat to set/get exfat volume label.
> > * Replace iconv library by standard C functions mbstowcs() and wcrtomb().
> > * Fix the build warnings/errors and add warning options.
> > * Fix several bugs(memory leak, wrong endian conversion, zero out
> > beyond end of file) and cleanup codes
> > * Fix issues on big endian system and on 32bit system.
> > * Add support for Android build system.
> >
> > The git tree is at:
> >
> > https://protect2.fireeye.com/url?k=c2ec59b9-9f266c0e-c2edd2f6-0cc47a30
> > 03e8-e469846ab6add112&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > fatprogs
> >
> > The tarballs can be found at:
> >
> > https://protect2.fireeye.com/url?k=88473660-d58d03d7-8846bd2f-0cc47a30
> > 03e8-7bb3906eafbb32bc&q=1&u=https%3A%2F%2Fgithub.com%2Fexfatprogs%2Fex
> > fatprogs%2Freleases%2Ftag%2F1.0.2
> >
>
> Can we follow the standard of source tarballs be <projectname>-<version>.tar.gz? In this case, exfat-
> 1.0.2.tar.gz instead of 1.0.2.tar.gz?
Ah, When I tried to download it through this link, source tarballs was exfatprogs-1.0.2.tar.gz...
Am I missing something ?
>
> --
> Goldwyn
next prev parent reply other threads:[~2020-04-23 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200423084908epcas1p1b5d43c33b263b30844fc03a341f67413@epcas1p1.samsung.com>
2020-04-23 8:49 ` [ANNOUNCE] exfatprogs-1.0.2 version released Namjae Jeon
2020-04-23 13:43 ` Eric Sandeen
2020-04-23 23:35 ` Namjae Jeon
2020-04-23 14:44 ` 'Goldwyn Rodrigues'
2020-04-23 14:55 ` Eric Sandeen
2020-04-23 23:38 ` Namjae Jeon [this message]
2020-04-24 2:32 ` 'Goldwyn Rodrigues'
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='000101d619c8$5c6e3b90$154ab2b0$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=hyc.lee@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rgoldwyn@suse.de \
--cc=sandeen@sandeen.net \
--cc=sedat.dilek@gmail.com \
/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).