Add AnonAddy #1680

Closed
nitrohorse wants to merge 1 commits from 1673 into master
nitrohorse commented 2020-02-01 18:47:10 +00:00 (Migrated from github.com)

Description

Resolves: https://github.com/privacytoolsIO/privacytools.io/issues/1673

Check List

  • I understand that by not opening an issue about a software/service/similar addition/removal, this pull request will be closed without merging.

  • I have read and understand the contributing guidelines.

  • The project is Free Libre and/or Open Source Software

<!-- PLEASE READ OUR CODE OF CONDUCT (https://github.com/privacytoolsIO/privacytools.io/blob/master/CODE_OF_CONDUCT.md) AND CONTRIBUTING GUIDELINES (https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md) BEFORE SUBMITTING --> ## Description Resolves: https://github.com/privacytoolsIO/privacytools.io/issues/1673 #### Check List <!-- Please add an x in each box below, like so: [x] --> - [x] I understand that by not opening an issue about a software/service/similar addition/removal, this pull request will be closed without merging. - [x] I have read and understand [the contributing guidelines](https://github.com/privacytoolsIO/privacytools.io/blob/master/.github/CONTRIBUTING.md). - [x] The project is [Free Libre](https://en.wikipedia.org/wiki/Free_software) and/or [Open Source](https://en.wikipedia.org/wiki/Open-source_software) Software * Netlify preview for the mainly edited page: https://deploy-preview-1680--privacytools-io.netlify.com/providers/email/ * Code repository of the project (if applicable): https://github.com/anonaddy/anonaddy
netlify[bot] commented 2020-02-01 18:48:15 +00:00 (Migrated from github.com)

Deploy preview for privacytools-io ready!

Built with commit b6a34ed00b

https://deploy-preview-1680--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit b6a34ed00b88ba8ef53d6396733d430d029afb95 https://deploy-preview-1680--privacytools-io.netlify.com
Mikaela (Migrated from github.com) approved these changes 2020-02-02 15:23:09 +00:00
Mikaela (Migrated from github.com) left a comment

It looks OK to me, but I am not sure if it's a good idea to merge with #1672 in progress.

It looks OK to me, but I am not sure if it's a good idea to merge with #1672 in progress.
dngray commented 2020-02-03 02:32:41 +00:00 (Migrated from github.com)

It looks OK to me, but I am not sure if it's a good idea to merge with #1672 in progress.

Some of the layout/indenting has changed with #1672 this is going to cause a future conflict that will need to be resolved. It really can wait 26 days.

> It looks OK to me, but I am not sure if it's a good idea to merge with #1672 in progress. Some of the layout/indenting has changed with #1672 this is going to cause a future conflict that will need to be resolved. It really can wait 26 days.
Mikaela commented 2020-02-04 13:35:35 +00:00 (Migrated from github.com)

Agreed, sorry @nitrohorse.

Agreed, sorry @nitrohorse.
This repo is archived. You cannot comment on pull requests.
No reviewers
No Milestone
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1680
No description provided.