From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-devel@gnu.org
Subject: Re: Don't add tags to ELPA packages -- documentation?
Date: Tue, 17 Aug 2021 15:51:05 -0700 [thread overview]
Message-ID: <87fsv7ofc6.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mtpfenog.fsf@alphapapa.net> (Adam Porter's message of "Tue, 17 Aug 2021 17:01:03 -0500")
Adam Porter <adam@alphapapa.net> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>>> Can I patch the README to tell developers not to use tags at all?
>>>
>>> Sure.
>>> Indeed tags are not used in elpa.git and nongnu.git.
>>>
>>> Of course, you can still use tags there if you want, like in any
>>> other repository, but you're better off giving them names that include
>>> the relevant package's name, like `ebdb-0.7`.
>>
>> Good to know! I don't suppose you know what happens when we add ELPA or
>> nongnu ELPA as a new remote to a repo already containing tags that will
>> conflict with ELPA tags? Do you know at what stage git will bark at us?
>> Anyway, I can probably figure this out myself, but inquiring minds on
>> Matrix want to know...
>
> Well, that mind would be mine. :) Yes, I'd like to submit some of my
> packages (including some that are already on MELPA) to ELPA or nongnu
> ELPA at some point, but I tag my stable releases with tags like "0.6.1",
> which MELPA uses for MELPA Stable packages. It seems like I'd have to
> either delete the tags or rename them with the package name as a prefix,
> and AFAIK either one would be incompatible with MELPA Stable. Of
> course, I guess there'd be no need to be on MELPA anymore in that case,
> but having to fix all the tags would be a hassle, and then I'd have to
> break an old habit. I guess one can't have everything, but it'd be
> great if this could be "solved." The idea of sharing tags with other
> repos that aren't part of my own repos feels a little like a Twilight
> Zone episode, if there were an Emacs edition: they're not there, but
> they're there... :)
My first inkling of this issue came when I ran "git tag -l" in my EBDB
repo, and it returned hyperbole- and eglot-related tags. Talk about
Twilight Zone... I was planning to order up an exorcism on my repository.
next prev parent reply other threads:[~2021-08-17 22:51 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 [this message]
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
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=87fsv7ofc6.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=adam@alphapapa.net \
--cc=emacs-devel@gnu.org \
/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).