From 28ae70ebad8debd8aa7b521a693aa3de89ad84d6 Mon Sep 17 00:00:00 2001 From: Timothy J Fontaine Date: Tue, 4 Nov 2014 15:08:12 -0800 Subject: npm: Upgrade to v2.1.6 --- deps/npm/html/doc/misc/npm-disputes.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'deps/npm/html/doc/misc/npm-disputes.html') diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index e6bc9a6180..f59921e2e9 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -13,7 +13,7 @@

SYNOPSIS

  1. Get the author email with npm owner ls <pkgname>
    2. -
  2. Email the author, CC support@npmjs.com
    3. +
  3. Email the author, CC support@npmjs.com
  4. After a few weeks, if there's no resolution, we'll sort it out.

Don't squat on package names. Publish code or move out of the way.

@@ -51,12 +51,12 @@ Joe's appropriate course of action in each case is the same.

owner (Bob).
  • Joe emails Bob, explaining the situation as respectfully as possible, and what he would like to do with the module name. He -adds the npm support staff support@npmjs.com to the CC list of +adds the npm support staff support@npmjs.com to the CC list of the email. Mention in the email that Bob can run npm owner add joe foo to add Joe as an owner of the foo package.
  • After a reasonable amount of time, if Bob has not responded, or if Bob and Joe can't come to any sort of resolution, email support -support@npmjs.com and we'll sort it out. ("Reasonable" is +support@npmjs.com and we'll sort it out. ("Reasonable" is usually at least 4 weeks, but extra time is allowed around common holidays.)
    • @@ -97,8 +97,8 @@ things into it.

    If you see bad behavior like this, please report it right away.

    SEE ALSO

    @@ -112,5 +112,5 @@ things into it.        - + -- cgit v1.2.1