From: Christian Couder <firstname.lastname@example.org>
Cc: git <email@example.com>
Subject: Re: Handling the Git trademark
Date: Mon, 26 Sep 2022 17:25:53 +0200 [thread overview]
Message-ID: <CAP8UFD3pZLiyDFZTDdMH-_D+d0zp7q0MfiOujf82ZhrLULJwHQ@mail.gmail.com> (raw)
On Tue, Sep 20, 2022 at 10:38 AM Phillip Wood <firstname.lastname@example.org> wrote:
> Thanks for taking the time to start a discussion on this. My immediate
> reaction is that it would be a shame to lose control of the trademark by
> not enforcing it.
Thanks for your opinion on this!
> If it is taking up too much of the leadership
> committee's time perhaps we could consider asking for more volunteers to
> handle some of the load. Would a few people volunteering a couple of
> hours a month make a useful difference?
Yeah, I think that would make a difference. Thanks for the suggestion!
> One other thought is that there are a number of companies which use
> "git" in their name that benefit indirectly from the git project
> enforcing the trademark and thereby ensuring the name "git" is trusted.
> If we were ever in the unfortunate position of having to take time
> consuming (and presumably costly) legal action perhaps we could approach
> them for support?
Yeah, we have already thought about this, but we haven't needed such
prev parent reply other threads:[~2022-09-26 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 12:11 Handling the Git trademark Christian Couder
2022-09-20 8:38 ` Phillip Wood
2022-09-26 15:25 ` Christian Couder [this message]
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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).