From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: has anyone bothered to read this "Git is a security risk"?
Date: Tue, 14 Apr 2020 16:13:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2004141612580.6138@localhost.localdomain> (raw)
https://twitter.com/blubracket/status/1250123442600513547
rday
next reply other threads:[~2020-04-14 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 20:13 Robert P. J. Day [this message]
2020-04-14 20:17 ` has anyone bothered to read this "Git is a security risk"? Santiago Torres Arias
2020-04-15 9:55 ` Michal Suchánek
2020-04-14 20:35 ` Konstantin Ryabitsev
2020-04-14 20:58 ` Jason Pyeron
2020-04-14 21:03 ` Jason Pyeron
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=alpine.LFD.2.21.2004141612580.6138@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.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 NNTP newsgroup(s).