summaryrefslogtreecommitdiff
path: root/man/bundle-pristine.1.txt
diff options
context:
space:
mode:
authorhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2019-01-04 13:10:58 +0000
committerhsbt <hsbt@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>2019-01-04 13:10:58 +0000
commite97741e12a22d78825a3a9dfcb7382adb0e27855 (patch)
tree5344cb31a89df6fd5fbae92740d4229d655eee8f /man/bundle-pristine.1.txt
parent4bbbbb6a3f5bd242f740041a644311f97c4a0052 (diff)
Merge Bundler 2.0.1 from upstream.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'man/bundle-pristine.1.txt')
-rw-r--r--man/bundle-pristine.1.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/man/bundle-pristine.1.txt b/man/bundle-pristine.1.txt
index a46f3c830c..2fd320282a 100644
--- a/man/bundle-pristine.1.txt
+++ b/man/bundle-pristine.1.txt
@@ -18,9 +18,9 @@ BUNDLE-PRISTINE(1) BUNDLE-PRISTINE(1)
gem's git repository as if one were installing from scratch.
Note: the Bundler gem cannot be restored to its original state with
- 1mpristine22m. One also cannot use 1mbundle pristine 22mon gems with a 'path'
- option in the Gemfile, because bundler has no original copy it can
- restore from.
+ 1mpristine22m. One also cannot use 1mbundle pristine 22mon gems with a 'path' op-
+ tion in the Gemfile, because bundler has no original copy it can re-
+ store from.
When is it practical to use 1mbundle pristine22m?