News for hackers. Stuff that matters.
Re:How GDPR Will Change The Way You Develop by icebraining on Wednesday February 28, 2018 @03:45AM (#16481625)
Why are you accepting PII into your software projects' source repository in the first place?
Re:How GDPR Will Change The Way You Develop by PeterisP on Wednesday February 28, 2018 @07:57AM (#16482658)
Source repositories in many (most?) companies include the full names of the employees who authored every particular commit. This is PII. GDPR refers to all personal information you're handling, not excluding information of your employees.
Re:How GDPR Will Change The Way You Develop by OrganicMSG on Wednesday February 28, 2018 @07:35AM (#16482543)
The simple logical answer to that is that it is clearly impossible to blacklist.

The more specific answer is:

git config --global user.name "Your Name Comes Here"

git config --global user.email [email protected]

Also, looking up, you can undo a rebase with reflog, so even editing commits with an interactive rebase may not be enough to purge a git repo of identifiable information that people have entered.

Re:How GDPR Will Change The Way You Develop by rmc on Wednesday February 28, 2018 @08:07AM (#16482712)
I presume email addresses are PII?
Re:How GDPR Will Change The Way You Develop by naicuoctavian on Tuesday March 13, 2018 @10:19AM (#16576279)
Yes they are.