summaryrefslogtreecommitdiff
path: root/deps/npm/man/man1/registry.1
diff options
context:
space:
mode:
authorisaacs <i@izs.me>2012-08-06 13:07:31 -0700
committerisaacs <i@izs.me>2012-08-06 13:07:31 -0700
commitcaf69aa91a94c7c05574afc9fcc97f45aa8d5ea5 (patch)
tree1718d7bf764945e67deeae5758de67b9203d5c27 /deps/npm/man/man1/registry.1
parent9badc002b4b109b237466c14de08278ef9be1e90 (diff)
downloadnode-new-caf69aa91a94c7c05574afc9fcc97f45aa8d5ea5.tar.gz
npm: Upgrade to 1.1.47
Diffstat (limited to 'deps/npm/man/man1/registry.1')
-rw-r--r--deps/npm/man/man1/registry.14
1 files changed, 2 insertions, 2 deletions
diff --git a/deps/npm/man/man1/registry.1 b/deps/npm/man/man1/registry.1
index 3abf3f57fa..0565e8f2f9 100644
--- a/deps/npm/man/man1/registry.1
+++ b/deps/npm/man/man1/registry.1
@@ -1,4 +1,4 @@
-.\" Generated with Ronnjs/v0.1
+.\" Generated with Ronnjs 0.3.8
.\" http://github.com/kapouer/ronnjs/
.
.TH "NPM\-REGISTRY" "1" "August 2012" "" ""
@@ -40,7 +40,7 @@ to read any published packages, in addition to your private ones, and by
default will only publish internally\. If you then want to publish a
package for the whole world to see, you can simply override the \fB\-\-registry\fR config for that command\.
.
-.SH "I don\'t want my package published in the official registry\. It\'s private\."
+.SH "I don&#39;t want my package published in the official registry\. It&#39;s private\."
Set \fB"private": true\fR in your package\.json to prevent it from being
published at all, or \fB"publishConfig":{"registry":"http://my\-internal\-registry\.local"}\fR
to force it to be published only to your internal registry\.