From: Sven Ebenfeld <sven.ebenfeld@gmail.com>
To: openembedded-devel@lists.openembedded.org, martin.jansa@gmail.com
Subject: Re: [meta-filesystems][PATCH] f2fs-tools: Update to Version 1.04
Date: Wed, 03 Dec 2014 22:53:02 +0100 [thread overview]
Message-ID: <547F863E.7040109@gmail.com> (raw)
In-Reply-To: <20141203180619.GF2455@jama>
Am 03.12.2014 um 19:06 schrieb Martin Jansa:
> On Wed, Dec 03, 2014 at 12:14:01PM +0100, Sven Ebenfeld wrote:
>> Signed-off-by: Sven Ebenfeld <sven.ebenfeld@gmail.com>
>> ---
>
> The subject says 1.04 and recipe 1.4.0.
>
> Also next time remove old version (1.1.0).
I were not really sure what is "best practice". Next time, I will remove
the old version as well.
>
> And use f2fs-tools instead of "files" directory for slightly faster
> lookup.
>
> I've updated all 3 when cherry-picking to master-next.
Thanks for updating! I will use this feedback for my future patches.
prev parent reply other threads:[~2014-12-03 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 11:14 [meta-filesystems][PATCH] f2fs-tools: Update to Version 1.04 Sven Ebenfeld
2014-12-03 18:06 ` Martin Jansa
2014-12-03 21:53 ` Sven Ebenfeld [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=547F863E.7040109@gmail.com \
--to=sven.ebenfeld@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.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