Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: remove use of profanity in source #4122

Merged
merged 1 commit into from
Dec 2, 2015
Merged

meta: remove use of profanity in source #4122

merged 1 commit into from
Dec 2, 2015

Conversation

MylesBorins
Copy link
Contributor

The CoC requests to avoid the casual use of profanity.

@cjihrig
Copy link
Contributor

cjihrig commented Dec 2, 2015

LGTM

1 similar comment
@targos
Copy link
Member

targos commented Dec 2, 2015

LGTM

@mscdex mscdex added dns Issues and PRs related to the dns subsystem. benchmark Issues and PRs related to the benchmark subsystem. labels Dec 2, 2015
@mscdex
Copy link
Contributor

mscdex commented Dec 2, 2015

LGTM

The CoC requests to avoid the casual use of profanity.

PR-URL: #4122
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: targos - Michaël Zasso <[email protected]>
Reviewed-By: Brian White <[email protected]>
@MylesBorins
Copy link
Contributor Author

Landed in b619831

@MylesBorins MylesBorins merged commit b619831 into nodejs:master Dec 2, 2015
@MylesBorins MylesBorins deleted the merde branch December 2, 2015 19:07
@misterdjules
Copy link

@thealphanerd By choosing this branch name, you added two occurrences of profanity to this repository (three if we count the notification sent to the #io.js IRC channel). As a result, the net effect of this PR is questionable.

Please, don't choose such names for branches in the future, it makes the project look bad. Also, is there a way to make GitHub not show this branch name in this repository?

@MylesBorins
Copy link
Contributor Author

I apologize for the lapse of judgement it will not happen again. AFAIK there is no way to change the branch name in the PR

MylesBorins pushed a commit that referenced this pull request Dec 5, 2015
The CoC requests to avoid the casual use of profanity.

PR-URL: #4122
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: targos - Michaël Zasso <[email protected]>
Reviewed-By: Brian White <[email protected]>
@misterdjules
Copy link

@thealphanerd I contacted GitHub's support, and it seems that if you delete your own fork of nodejs/node, the branch name will not be visible in this PR. Then you can re-fork nodejs/node, and as long as you don't re-create a branch with the same name, the branch name will still not be displayed in this PR.

Can you please do that?

@MylesBorins
Copy link
Contributor Author

@misterdjules done

Thanks for following up

@misterdjules
Copy link

@thealphanerd Excellent, thank you for your help, very much appreciated! 👍

MylesBorins pushed a commit that referenced this pull request Dec 15, 2015
The CoC requests to avoid the casual use of profanity.

PR-URL: #4122
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: targos - Michaël Zasso <[email protected]>
Reviewed-By: Brian White <[email protected]>
@jasnell jasnell mentioned this pull request Dec 17, 2015
MylesBorins pushed a commit that referenced this pull request Dec 17, 2015
The CoC requests to avoid the casual use of profanity.

PR-URL: #4122
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: targos - Michaël Zasso <[email protected]>
Reviewed-By: Brian White <[email protected]>
MylesBorins pushed a commit that referenced this pull request Dec 23, 2015
The CoC requests to avoid the casual use of profanity.

PR-URL: #4122
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: targos - Michaël Zasso <[email protected]>
Reviewed-By: Brian White <[email protected]>
scovetta pushed a commit to scovetta/node that referenced this pull request Apr 2, 2016
The CoC requests to avoid the casual use of profanity.

PR-URL: nodejs#4122
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: targos - Michaël Zasso <[email protected]>
Reviewed-By: Brian White <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmark Issues and PRs related to the benchmark subsystem. dns Issues and PRs related to the dns subsystem.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants