From: "alison.fung@159group.com" <alison.fung@159group.com>
To: linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: Rapid Prototyping & Molding Manufacturing & OEM service2014-01-22 19:33:09
Date: Wed, 22 Jan 2014 19:33:14 +0800 [thread overview]
Message-ID: <52dfac01.0466420a.3b68.ffff9705@mx.google.com> (raw)
[-- Attachment #1: Type: text/html, Size: 1029 bytes --]
[-- Attachment #2: Type: text/plain, Size: 388 bytes --]
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
[-- Attachment #3: Type: text/plain, Size: 179 bytes --]
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
reply other threads:[~2014-01-22 11:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52dfac01.0466420a.3b68.ffff9705@mx.google.com \
--to=alison.fung@159group.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=powstar01@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).