|
From: | Dmitry Gutov |
Subject: | Re: policy discussion on bundling ELPA packages in the emacs tarball |
Date: | Sun, 24 Jan 2021 04:28:09 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 |
On 23.01.2021 11:57, Eli Zaretskii wrote:
I've played with 'git submodules' on Windows mingw64. You can pass a local ELPA repository to 'git submodules add', but it copies the whole thing into the emacs repository:It is quite clear that ELPA will need some changes on its side to support this integration. One such change is to have branches that roughly correspond to Emacs's 'master' and 'release' branches, because we would want to have only the stable branches of the ELPA packages to be visible on the Emacs's release branch.
Or the package maintainers could bump the submodule refs manually from time to time.
There is not a way to specify the branch in the 'git submodule add' commandAFAIU, you can do that in the .gitmodules file.
'man git submodule' mentions the -b option:add [-b <branch>] [-f|--force] [--name <name>] [--reference <repository>] [--depth <depth>] [--] <repository> [<path>]
[Prev in Thread] | Current Thread | [Next in Thread] |