From: Jessie <jessie06326@163.com>
To: gcc-patches@gcc.gnu.org
Subject: quote
Date: Sat, 11 May 2024 11:22:52 +0800 (CST) [thread overview]
Message-ID: <420a8130.3137.18f65acc33e.Coremail.jessie06326@163.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 190 bytes --]
We are the industrial hose supplier in China.
Do you need that kind hose?
More information and catalog can be send if you need.
Waiting for your news.
Best regards
Jessie
next reply other threads:[~2024-05-11 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 3:22 Jessie [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-14 8:35 quote Jessie Xu
2024-01-26 7:15 quote Xu Jessie
2023-10-31 8:29 Quote Jessie
2023-10-31 8:24 quote Jessie
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=420a8130.3137.18f65acc33e.Coremail.jessie06326@163.com \
--to=jessie06326@163.com \
--cc=gcc-patches@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).