From: "Kapiton Khariton" <kapitonkhariton@bk.ru>
To: provos@citi.umich.edu, dugsong@monkey.org, mike@datanerds.net,
yegorushkin@gmail.com, newlib@sourceware.org
Subject: Fwd[13]: Fmt
Date: Mon, 13 Apr 2020 23:43:00 +0300 [thread overview]
Message-ID: <1586810580.409499439@f129.i.mail.ru> (raw)
We can offer the following edible/cooking oil; Soybean Oil, Refined Sunflower Oil, Corn Oil, Peanut Oil, RBD Palm Olein Oil CP 10,8, Rapeseed/Canola Oil, Sesame Oil, Refined Coconut Oil, Extensive range of bakery fats,
PAYMENT TERMS:
Very Flexible with payment, but basically we accept 100% at sight LC after initial Pre-production
command.
PACKING CONDITIONS:
20ft Container, Bulk/Flexi tanks, In Bottles 1L, 3L,5L, Jerry Cans, 18L, 25L, 18L Gorse Weight Tin Square Pack. | Packing can be adapted based on customer’s choice.
Kapiton Khariton
reply other threads:[~2020-04-13 20:43 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=1586810580.409499439@f129.i.mail.ru \
--to=kapitonkhariton@bk.ru \
--cc=dugsong@monkey.org \
--cc=mike@datanerds.net \
--cc=newlib@sourceware.org \
--cc=provos@citi.umich.edu \
--cc=yegorushkin@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 read-only IMAP folder(s) and NNTP newsgroup(s).