branch: elpa-admin
commit f85cb8d6aa617bc999783e3703eaae402dc7f5a5
Author: Stefan Monnier <[email protected]>
Commit: Stefan Monnier <[email protected]>
* README (PACKAGES/Externals): Clarify use
Don't give the impression that there's a need to checkout
the whole elpa.git archive. Suggested by Feng Shu <[email protected]>.
---
README | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/README b/README
index 8c85210..b827780 100644
--- a/README
+++ b/README
@@ -234,10 +234,12 @@ new remote branch in `elpa.git', named
externals/<pkgname>. For example:
git push elpa <mybranch>:externals/<pkgname>
Then edit the `externals-list' file as mentioned above, and push that
-change to `elpa's master branch.
+change to `elpa's master branch. After it's added to the `externals-list'
+file, the package can be maintained just by pushing changes to the
+`externals/<pkgname>` branch.
-You can check out all the external packages into the `packages' directory
-with the command:
+If you wish to check out all the external packages into the `packages'
+directory, you can run the command:
make externals
