linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Nick Krause <xerofoify@gmail.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: New to F2FS
Date: Thu, 21 Aug 2014 22:17:41 -0400	[thread overview]
Message-ID: <CAPDOMVgc4vw+kG4kQfhX8Kph6cSOq2-eP25ja2NBa4noKy1f8A@mail.gmail.com> (raw)
In-Reply-To: <20140821205321.GD85961@jaegeuk-mac02.mot-mobility.com>

On Thu, Aug 21, 2014 at 4:53 PM, Jaegeuk Kim <jaegeuk@kernel.org> wrote:
> Hi,
>
> On Tue, Aug 19, 2014 at 06:02:03PM -0400, Nick Krause wrote:
>> Hey fellow developers,
>> I am new to f2fs and are wondering where to start , I assume reading
>> the f2fs docs in the kernel tree is
>> a good place to start.
>
> It depends on your background. :)
> If you're familiar with filesystem, it would be good to read f2fs docs in the
> kernel tree or external links in the f2fs wiki.
>
> Thanks,
>
>> Regards and Thanks Nick
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.
>> Video for Nerds.  Stuff that matters.
>> http://tv.slashdot.org/
>> _______________________________________________
>> Linux-f2fs-devel mailing list
>> Linux-f2fs-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
Where is the wiki, after goggling seems I didn't find it.
Nick

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/

  reply	other threads:[~2014-08-22  2:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 22:02 New to F2FS Nick Krause
2014-08-21 20:53 ` Jaegeuk Kim
2014-08-22  2:17   ` Nick Krause [this message]
2014-08-22 20:59     ` Jaegeuk Kim
2014-08-23  2:21       ` Nick Krause

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=CAPDOMVgc4vw+kG4kQfhX8Kph6cSOq2-eP25ja2NBa4noKy1f8A@mail.gmail.com \
    --to=xerofoify@gmail.com \
    --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).