public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: sales LLC <Sarah.Radix@praqua.com>
To: java@gcc.gnu.org
Cc: carlo.lazzari@praqua.com
Subject: Re:  invoice of 5392, 53912020
Date: 23 Mar 2020 23:21:00 -0700	[thread overview]
Message-ID: <20200323232100.FE339427D217E661@praqua.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 395 bytes --]

Dear Sir,



Please revise the invoice of 5392, 5391 and submit it again with original stamp and signature to project site as soon as possible. Please note that the company’s full name should be:

included in full. Thank you.



Best regards,



Jia (Stella) Zhou / 周嘉

MEP Division丨Dubai Silicon Park Project丨Quantity Survey



cid:image001.png@01D52507.302F4260

[-- Attachment #2: invoice of 5392, 53912020.gz --]
[-- Type: application/octet-stream, Size: 423669 bytes --]

                 reply	other threads:[~2020-03-23 23:21 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=20200323232100.FE339427D217E661@praqua.com \
    --to=sarah.radix@praqua.com \
    --cc=carlo.lazzari@praqua.com \
    --cc=java@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).