git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Paul Smith <paul@mad-scientist.net>
To: Jakub Trzebiatowski <cubuspl42.1@gmail.com>,
	Jason Pyeron <jpyeron@pdinc.us>
Cc: git@vger.kernel.org, Matthew Horowitz <mhorowitz@pdinc.us>
Subject: Re: Is git compliant with GDPR?
Date: Thu, 02 Jul 2020 14:38:03 -0400	[thread overview]
Message-ID: <03bd4b4e9b172c4ee6cb44653bb9c5b26df76445.camel@mad-scientist.net> (raw)
In-Reply-To: <CAAF2pWb8Namk1rpm4==PUrq4ft9fp4eD=t9WyMLv56dPZuGk2g@mail.gmail.com>

On Thu, 2020-07-02 at 19:06 +0200, Jakub Trzebiatowski wrote:
> But you said that git itself (as a software) doesn't fall under GDPR,
> and that's the only thing I'm not sure about. I was wondering if
> someone with a deeper understanding of GDPR would tell my _why_. 
> Because when interpreting the law literally, it sounds like it does.

You might be interested in reading the conversation that was had on
this list the last time this subject was raised, in 2018:

https://public-inbox.org/git/5587534.o6tcmYBVvN@mfick-lnx/T/

I can't say whether it will satisfy you or not.


  reply	other threads:[~2020-07-02 19:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 15:58 Is git compliant with GDPR? Jakub Trzebiatowski
2020-07-02 16:28 ` Jason Pyeron
2020-07-02 16:40   ` Randall S. Becker
2020-07-03  6:22     ` demerphq
2020-07-03 13:52       ` Randall S. Becker
2020-07-02 17:06   ` Jakub Trzebiatowski
2020-07-02 18:38     ` Paul Smith [this message]
2020-07-02 19:25       ` Jason Pyeron
2020-07-03  6:29         ` demerphq
2020-07-02 18:47     ` 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

  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 \
    --in-reply-to=03bd4b4e9b172c4ee6cb44653bb9c5b26df76445.camel@mad-scientist.net \
    --to=paul@mad-scientist.net \
    --cc=cubuspl42.1@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jpyeron@pdinc.us \
    --cc=mhorowitz@pdinc.us \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).