Re: Don't add tags to ELPA packages -- documentation?

[Eric Abrahamsen <eric@ericabrahamsen.net>]

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Kévin Le Gouguec [2021-08-18 16:26:33] wrote:
>>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>>> Not sure where they come from.
>>>
>>> FWIW, this can be examined with Git, e.g.:
>>>
>>> $ git branch --remote --contains 0.10
>>>   origin/externals/eglot
>>> $ git branch --remote --contains 1.3.0
>>>   origin/externals/disk-usage
>>
>> Thanks, but by "where" I meant "which kind of operations".
>> IOW, how did they end up there?
>
> Developers of those packages would have had to explicitly push them to
> elpa.git.

How does this look?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: elpa-mention-tags.diff --]
[-- Type: text/x-patch, Size: 862 bytes --]

diff --git a/README b/README
index 8a549a6e71..4377f6a43b 100644
--- a/README
+++ b/README
@@ -212,6 +212,17 @@ if it is not your own code, make sure the author has signed the relevant
 copyright papers (for non-trivial contributions), and indicate the author
 correctly in the commit.
 
+** Tags
+
+Git tags should not be pushed to the =elpa.git= repository.  Git tags
+are global throughout a repository, and it is highly likely that tags
+in one package will clash with those in others.  Furthermore, tags
+play no functional role in ELPA repositories.
+
+Developers are welcome to continue using tags locally: so long as they
+are not pushed to the public repository, no conflicts will occur.  Git
+will not push tags without being explicitly told to do so.
+
 ** External branches
 
 A copy of the code of every package is kept in the =elpa.git= repository