From: demerphq <demerphq@gmail.com>
To: Jason Pyeron <jpyeron@pdinc.us>
Cc: Git <git@vger.kernel.org>, Matthew Horowitz <mhorowitz@pdinc.us>,
Jakub Trzebiatowski <cubuspl42.1@gmail.com>,
paul@mad-scientist.net
Subject: Re: Is git compliant with GDPR?
Date: Fri, 3 Jul 2020 08:29:07 +0200 [thread overview]
Message-ID: <CANgJU+X2C157XCxbcdrGf1rRWY10o9UGtXMaqafgJBLORucEkw@mail.gmail.com> (raw)
In-Reply-To: <0f0e01d650a6$9a5b5b80$cf121280$@pdinc.us>
On Thu, 2 Jul 2020 at 21:27, Jason Pyeron <jpyeron@pdinc.us> wrote:
> > On Sun, Jun 03, 2018 at 04:28:31PM +0100, Philip Oakley wrote:
> <snip/>
> > You provide a lot of arguments about why it is not a necessity to have
> > this, but let's assume it is; is there any actual problem you see with
> > the proposal, except that someone would have to implement it?
>
> It's the strawman problem. If it was a real 'real issue' then it would have
> already shown up with companies clamouring to pay folk to fix our (git's)
> latest problem. But the haven't, so I think it's a much more balanced issue.
>
I don't agree. These things tend to come in waves. Just because the
first wave hasnt hit yet doesn't mean it wont come. GDPR is still
super new, people are still coming to understand it. Over time this
understanding will lead to more people exercising the right to be
forgotten.
cheers,
Yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
next prev parent reply other threads:[~2020-07-03 6:29 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
2020-07-02 19:25 ` Jason Pyeron
2020-07-03 6:29 ` demerphq [this message]
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=CANgJU+X2C157XCxbcdrGf1rRWY10o9UGtXMaqafgJBLORucEkw@mail.gmail.com \
--to=demerphq@gmail.com \
--cc=cubuspl42.1@gmail.com \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
--cc=mhorowitz@pdinc.us \
--cc=paul@mad-scientist.net \
/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).