From: peppermint@tutanota.de
To: Gcc Help <gcc-help@gcc.gnu.org>
Subject: Gcc Use
Date: Fri, 26 Apr 2024 06:34:40 +0200 (CEST) [thread overview]
Message-ID: <NwNflQs--3-9@tutanota.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Hello, sorry but I was wondering if I could have some clarification on an issue with the acronym.
See, I'm an aspiring artist, and I want to make an independent comic book. I wanted to call my independent comic label Ghoulish Colour Comics, which, when abbreviated, becomes GCC.
I didn't want to cause any sort of like brand confusion for people, but I wouldn't be making software, I would be making comic books, so I don't think there would be any type of confusion in people's minds about it.
A part of me wanted to just assume it would be fine, but another part of me said it would be be best to shoot you guys an email first and get your take on the issue.
If necessary, I'm willing to put some kind of disclaimer or something in my works saying i'm not affiliated with the FSF or GNU or anything like that, if that would help.
sorry if i'm rambling. Thank you for taking the time to read my letter.
--
Sent with Tuta; enjoy secure & ad-free emails:
https://tuta.com
next reply other threads:[~2024-04-26 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 4:34 peppermint [this message]
2024-04-26 8:44 ` Jonathan Wakely
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=NwNflQs--3-9@tutanota.de \
--to=peppermint@tutanota.de \
--cc=gcc-help@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).