From: Kat Sarmiento <ksarmiento.content@gmail.com>
To: gcc@gcc.gnu.org
Subject: Can I write for you?
Date: Fri, 27 Jan 2023 15:01:06 +0000 [thread overview]
Message-ID: <CALsN14_xyTPxRY6kpFFr1fQ2gqJdfdCKiENnvW0DmxP2aoGG6w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
Hello — Kat here. Can I write for you? It’s absolutely free of charge, I
was just hoping for a legit platform to welcome some of my written works.
Trying out a new career path (it’s a loooong story) which requires a couple
of published articles and a bit of name dropping, and I was wondering if I
can drop yours?
Would very very much appreciate the opportunity. Please let me know if it’s
possible?
Thanks for your time!
Warmly,
Kat
[image: Logo]
Kat Sarmiento
Content Writer
ᐧ
reply other threads:[~2023-01-27 15:01 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=CALsN14_xyTPxRY6kpFFr1fQ2gqJdfdCKiENnvW0DmxP2aoGG6w@mail.gmail.com \
--to=ksarmiento.content@gmail.com \
--cc=gcc@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).