From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Yuan Fu" <casouri@gmail.com>,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>,
"Bozhidar Batsov" <bozhidar@batsov.dev>,
"Emacs Devel" <emacs-devel@gnu.org>
Subject: Re: Don't add tags to ELPA packages -- documentation?
Date: Wed, 18 Aug 2021 09:56:49 -0700 [thread overview]
Message-ID: <87zgtelmi6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874kbmn41j.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Wed, 18 Aug 2021 08:52:40 -0700")
[-- 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
next prev parent reply other threads:[~2021-08-18 16:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 21:10 Don't add tags to ELPA packages -- documentation? Eric Abrahamsen
2021-08-17 21:24 ` Stefan Monnier
2021-08-17 21:51 ` Eric Abrahamsen
2021-08-17 22:01 ` Adam Porter
2021-08-17 22:51 ` Eric Abrahamsen
2021-08-17 23:04 ` Stefan Monnier
2021-08-17 23:15 ` Phil Sainty
2021-08-17 23:28 ` Phil Sainty
2021-08-17 23:36 ` Eric Abrahamsen
2021-08-18 2:30 ` Phil Sainty
2021-08-18 6:41 ` Bozhidar Batsov
2021-08-18 7:03 ` Yuan Fu
2021-08-18 13:25 ` Stefan Monnier
2021-08-18 13:31 ` Stefan Monnier
2021-08-18 14:26 ` Kévin Le Gouguec
2021-08-18 14:33 ` Stefan Monnier
2021-08-18 15:52 ` Eric Abrahamsen
2021-08-18 16:56 ` Eric Abrahamsen [this message]
2021-08-18 19:43 ` Kévin Le Gouguec
2021-08-18 23:07 ` Stefan Monnier
2021-08-19 20:54 ` Jonas Bernoulli
2021-08-19 23:38 ` Eric Abrahamsen
2021-08-20 7:11 ` Andreas Schwab
2021-08-20 15:59 ` Eric Abrahamsen
2021-08-19 23:44 ` Eric Abrahamsen
2021-08-18 7:21 ` Phil Sainty
2021-08-18 8:15 ` Bozhidar Batsov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgtelmi6.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=bozhidar@batsov.dev \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).