>From b33289dab83b5f5abe93e4385d322fbfe36a1b27 Mon Sep 17 00:00:00 2001 From: Eric Abrahamsen Date: Mon, 14 Aug 2017 08:56:11 -0700 Subject: [PATCH] Add explicit instructions for new external packages * README: Spell out the process for new external packages. --- README | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/README b/README index 322392997..48c105994 100644 --- a/README +++ b/README @@ -194,6 +194,15 @@ help and only gets in the way. In the `external' case, the copy of the code is not kept here but in the `externals/' branch in the `elpa' repository. +To add a new externals package, first add this `elpa' repository as a +new remote in your existing repository. Then push a local branch to a +new remote branch in `elpa', named externals/. For example: + + git push elpa master:externals/ + +Then edit the `externals-list' file as mentioned above, and push that +change to `elpa's master branch. + You can check out all the external packages into the `packages' directory with the command: -- 2.14.1